I tried to set CI/CD with Kubernetes on AWS EC2 server using GitLab as following their guideline on the GitLab page, but I faced an error message that says the "API URL is blocked." and I saw the solution of that has to allow the options on the admin's page. But the thing is I can not find the admin area on my account. I guess I need to upgrade my account or something if I want to use its page.
BTW, I want to know both how I can find my admin's page on GitLab and guide of set CI/CD with Kubernetes on GitLab as on-premise.
Please advise to me. Thx in advance.
Related
can someone help point a direction how to setup Azure Webapp with CD / CI please?
I have a github repo, which i want to connect to a url, when the master branch is updated.
I tried following tutorial, and try setup https://dev.azure.com/ account, to which I'm not sure how, but the url : http://bss-olr.azurewebsites.net/ seems to have been connected, although i cant see how to take down the github workflow. (ie: I want to take it down, and reuse the same URL again)
Can someone help point the right direction? Azure is quite confusing with many outdated documentations.. Thanks in advance.
You should check out this updated Azure tutorial: Continuous deployment to Azure App Service. It shows you how to enable continuous deployment for your web app via the Azure portal.
Based on your description, you could try to use the Azure CLI to remove the linked deployment resource.
For example:
az webapp deployment source delete --name MyWebApp --resource-group MyResourceGroup
For more detailed steps , you could refer to this doc: az webapp deployment source delete
When I try to update the environment variables on an Azure DevOps release pipeline, I get the error below.
GitHub Could not create service hooks subscription Unable to configure a service on the selected GitHub repository. GitHub returned the error 'Resource not accessible by integration'.
I am an admin on the GitHub repo.
In Get sources, it is currently configured for a GitHub OAuth Service Connection. Another user is able to update the environment variables. I am using GitHub (not enterprise).
Is this an Azure DevOps permission that I do not have?
Is this an Azure DevOps permission that I do not have?
This error message usually comes with GitHub App installation token service connection.
Go Project Settings => Service Connections to check the details of the specific service connection. If your service connection is GitHub App installation token based service connection, then it's expected behavior to meet that issue. Our team are working on adding that support so far, please check this ticket.
Workaround:
1.Create a new service connection with OAuth/PAT method and use it in your pipeline. Since you're admin of the github repo, a Github PAT is more recommended.
2.If you have permission to the service connections and to the pipeline, this issue won't occur. Ask your Azure Devops project admin to via manage security.
After working with ADO tech support, it was discovered that we needed to remove the artifact and trigger definition from the release pipeline, and then re-add it. It is believed that there was cached service connection, and this updated the pointer to the correct service connection.
I was facing a similar issue when attempting to enable CI for a build and found this article and after digging in deeper I discovered that the issue was the actual PAT we created for the automation. What we missed originally was enabling the admin:repo_hook for the repository. This took longer to uncover than it should have, but just wanted to add that, as removing and re-adding things didn't really do anything for us.
I was wondering if there is any way to configure review apps in Spinnaker like Heroku or Gitlab have? Looked through documentation and forums and couldn't find anything. Just verifying.
You can trigger spinnaker pipeline using merge request event from GitLaband deploy your app under review to separeate namespace.
The main task is to implement correct lifecycle and clear obsolate applications using Spinnaker pipelines. But it is possible with current Spinnaker's functionality.
I want to use github to deploy my webapp on Azure. I setup github on Azure as my deployment source. But since I have a custom domain instead of using the free azurewebsits.net, I think I am having issues seeing the website from github. The webhook on github shows azurewebsites.net.... same on azure. I can edit the webhook on github but can't on Azure. What is the best way to integrate github with azure with a custom domain?
You don't need to edit the webhook on github, let it stick with the default sitename.azurewebsites.net.
When you setup a custom domain name, your default domain name (sitename.azurewebsites.net) still keeps working. Github will use that to deploy to your site
I have a GitHub hook for a new check-in, but it is not being received by Jenkins (running on a RedHat OpenShift cartridge).
Setup
RedHat OpenShift cartridge running Jenkins
Jenkins plugins in-play
GitHub plugin v1.8
Github Authentication plugin v0.14
Jenkins GIT client plugin v1.4.5
Jenkins GIT plugin v2.0
Public GitHub repository
Debugging
I have narrowed it down specifically to GitHub communicating with OpenShift, but am unsure how to troubleshoot any further, or resolve the issue. To narrow it down, I performed the following steps:
Configured one of each of the following types of Service Hooks in GitHub and captured the results in RequestBin
WebHook URL
Jenkins GitHub Plugin
Jenkins Git Plugin
I then ran Test Hook from GitHub
I took the resultant headers and payload from each RequestBin and manually created a POST request in Fiddler, pointing to the webhook endpoint
I saw some action on Jenkins by logging against com.cloudbees.jenkins.GitHubWebHook
However, the Test Hook from GitHub and checking into the repository never reached the server, at least not as evidenced by the logs.
I believe I have narrowed it down to an SSL issue. GitHub will not post the webhook to an OpenShift configured Jenkins cartridge, because it only responds to SSL/HTTPS. I am not sure of the specifics of how the canned Jenkins cartridge is configured, or how to change whether or not it uses SSL.
It is possible to change whether or not the OpenShift cartridge uses SSL, but I did not want to spend the time to get into it. The solution is to create your own cartridge definition, where you can specify all the settings, specifically which endpoints get created. Here is the OpenShift reference to generate the proper endpoints in case anyone wants to go that route.
I believe I have narrowed it down to an SSL issue. GitHub will not post the webhook to an OpenShift configured Jenkins cartridge, because it only responds to SSL/HTTPS. I am not sure of the specifics of how the canned Jenkins cartridge is configured, or how to change whether or not it uses SSL.
It is possible to change whether or not the OpenShift cartridge uses SSL, but I did not want to spend the time to get into it. The solution is to create your own cartridge definition, where you can specify all the settings, specifically which endpoints get created. Here is the OpenShift reference to generate the proper endpoints in case anyone wants to go that route.