I had a cloud build trigger that would run tests on pull request.
Then I disabled the trigger and then deleted it. But it still shows up in Github PR. How can I remove it?
After deleting the trigger from Cloud Build, I also had to remove it from Github repository settings:
Related
Our Company used to self-host GitLab for source-code management and configured webhook on gitlab to trigger all the project pipelines on jenkins. Initially, the gitlab url was 'https://git.fulcrumdigital.com' and later for an upgraded version, they changed url to 'https://autobuild.fulcrumdigital.com'
Recently, we migrated to 'github.com' and created an organization. The source codes for various projects are found under this organization, which is private. Now, when I try to configure webhooks for these projects, I see that they deliver as intended to jenkins, but jenkins doesn't trigger the respective project's build. Instead, it gives out a message as shown below.
jenkins-github webhook error
I don't find any info regarding this webhook on global configuration page.
Here is a snapshot of jenkins logs
jenkins logs
I don't face this webhook issue for newly created pipeline-projects on jenkins. I face this issue for older pipeline-projects that already had their webhook configured earlier for gitlab.
Help me to resolve this issue and make jenkins trigger build from github webhook for older pipeline-projects.
Did you try force regenerating the webhooks?
Go to Manage Jenkins > Configure System > GitHub plugin > Advance > Re-registers hooks for all jobs.
I had this problem myself. The first thing you want to do is go to Manage Jenkins -> Configure System scroll down to the GitHub section and click on "Advanced". You will see this:
It's important to have access to your Jenkins log (I'm running Jenkins with Docker). When I clicked on Re-register hooks for all jobs, I got the following error:
In my case, the error mentioned something with my access token. So, I checked my Github personal access token and it turned out, I need to turn on Read and Write for Webhook:
Now, go back to Jenkins and click on Re-register hooks for all jobs again, and on the next push, the build was automatically triggered.
I've an issue with two existing pipelines that refuse to queue any build on PR.
Every repository in our organisation has its own build policy on master & release/ branches.
The message in the PR is "1 required check broken: Unable to queue Build".
Others existing pipelines are working correctly.
In these two repositories I can trigger a pipeline build manually but not automatically.
I've tried to deactivate the existing build policy or to delete it and recreate it but without success. When I try to delete the existing pipeline I encounter the error : «TF400898: An Internal Error Occurred. Activity Id: .».
I've successfully managed to delete an existing pipeline from an old repository, so I have the permission to delete a pipeline.
Any hint ?
Please check if you have selected the do not queue new builds option in your pipeline. It should work normally if you change it to the Enabled option.
I've been using Azure DevOps for a while now, and CI has been working great. I commit to my branch, and it kicks off a branch automatically.
This has all of the sudden just stopped working.
I have tried all of the ideas from this question:
VSTS continuous integration triggers not working
But I cannot get it to trigger the build automatically.
Please help!
I faced the same issue and the fix was to delete unwanted GitHub service connections in 'Project Settings'. Multiple service connections using oauth and azure pipeline to same GitHub account was present. Once it is removed, pipelines were getting triggered automatically.
Azure DevOps CI trigger is not working even though the setting is set
Some times service event( https://status.dev.azure.com/ ) in Azure DevOps may cause this issue. Besides, if there is [skip ci] in commit message, the build will skip the CI trigger.
Check the document Skipping CI for individual commits for some more details.
Besides, if it still does not work now, try to manually Queue a build, then commit to to your branch again and check if it works for you. If not, try to create a new build pipeline to check if still have this issue.
Hope this helps.
I have many projects which uses Google Cloud Build + Github build pipeline setup. However, there is this one project, which I cannot create a webhook in Github for.
It used to work - but commits to the repository doesn't trigger the build process any more. I deleted the trigger and added it again - but the webhook in Github is not created automatically for this project.
When I run the trigger manually, it picks the wrong, but fixed commit which I did before an year.
Any clue?
Could you try delete a repository on Cloud Source Repositories and setup Google Cloud Build again ?
See:
https://cloud.google.com/cloud-build/docs/running-builds/automate-builds
Note: For external repositories, such as GitHub and Bitbucket, you must have owner-level permissions for the Cloud Platform project with which you're working. When you set up a build trigger with an external repository for the first time, you'll need to set up authorization with that repository.
After you've set up your external repository, Cloud Source Repository creates a mirror of your repository.
https://source.cloud.google.com
https://cloud.google.com/source-repositories/docs/deleting-a-repository
https://cloud.google.com/source-repositories/docs/mirroring-a-github-repository
I am experiencing the same issue. I can create a trigger for a repo, but I cannot connect the repo automatically to cloud build. We also have many projects, and this manual labor is sort of annoying.
Is there any (under the hood) github/gcloud api available in which I can connect a github repo to cloud build? I am aware that this can only be done by someone with admin privileges on a repo or organization in github.
After this, I will be able to run the command gcloud build triggers create github [NAME]
I've found many sites that describe how to trigger a build on a Jenkins machine whenever new code is pushed to a Github repository. One thing that keeps showing up repeatedly is to check the "Build when a change is pushed to GitHub" item under the Build Triggers section..
Unfortunately, no matter what I do I can't seem to get that item to show up as an option for me under Build Triggers.
I've even removed and re-installed Jenkins from scratch. When I install it, I just tell it to install all of the most common plugins. I've verified in the Jenkins configuration that the GitHub plugin is there.
What am I missing to trigger a build on a GitHub repo update?
According to https://wiki.jenkins-ci.org/display/JENKINS/GitHub+Plugin#GitHubPlugin-PluginInformation this was changed from
Build when a change is pushed to GitHub
to
GitHub hook trigger for GITScm polling
So it is sufficient to have GitHub Plugin installed.