I recently started using the Github Pull Request Plugin on Jenkins and notice on the PR it says default - build passed or failed.
Does anyone know where the label default is getting generated from? I looked through the configuration on Jenkins but was not able to see where it is pulling that from.enter image description here
Related
I have some problems with getting GitHub Pull Request Builder to work.
While configuring this plugin I used all of the given tests to check:
basic connection to GitHub
permissions to a repository
adding comment to pull-request
updating commit status
All of these things work right, but issuing pullrequest does not trigger the pipeline start. All I was able to get out of Jenkins logs is just an info that pr is being checked...jenkins_logs
Have anyone run into the same trouble? I can't find a solution to this problem.
I am using the Jenkins plugin GitHub Pull Request Builder to run some commands, and then update the status of my Pull Request.
The job is correctly triggering when I update a PR on GitHub, however I cannot get the job to update the status of the build on GitHub.
I have closely replicated the steps outlined in this article: https://medium.com/#mreigen/integrate-jenkins-builds-into-github-pull-requests-33bc053d6210
When I check the System Logs, I see this error: GitHub project property is missing the URL, cannot start ghprb trigger for job
I have entered the URL everywhere I can find to enter it, but so far nothing has worked.
This is my configuraiton for the plugin:
Any help on how to get the job to successfully add a status message to the Pull Request on GitHub would be greatly appreciated!
On the GitHub Pull Request Builder section of the Build Triggers, enabling the checkbox:
Build every pull request automatically without asking enables the Jenkins job to add an update status to GitHub.
You need to enable the github project option and provide your gihub url there.
The Bitbucket Pull Request Builder plugin for Jenkins allows Jenkins build to be triggers when Pull requests are created or commented on in Bitbucket.
This has been working fine for us, but on one particular repo, it has started failing.
The logs show:
WARNING: bitbucketpullrequestbuilder.bitbucketpullrequestbuilder.BitbucketBuildTrigger.run() failed for hudson.model.FreeStyleProject#2840d594[ci-metadata-app-new]
java.lang.NullPointerException
at bitbucketpullrequestbuilder.bitbucketpullrequestbuilder.BitbucketRepository.postBuildTagInTTPComment(BitbucketRepository.java:182)
at bitbucketpullrequestbuilder.bitbucketpullrequestbuilder.BitbucketRepository.isBuildTarget(BitbucketRepository.java:253)
at bitbucketpullrequestbuilder.bitbucketpullrequestbuilder.BitbucketRepository.getTargetPullRequests(BitbucketRepository.java:94)
at bitbucketpullrequestbuilder.bitbucketpullrequestbuilder.BitbucketPullRequestsBuilder.run(BitbucketPullRequestsBuilder.java:37)
at bitbucketpullrequestbuilder.bitbucketpullrequestbuilder.BitbucketBuildTrigger.run(BitbucketBuildTrigger.java:187)
It looks like the plugin can't post a comment to the Bitbucket API
postBuildTagInTTPComment
Which is preventing the build from triggering.
Has anyone seen this issue before? It is only happening for this particular repo.
Eventually cleared it by deleting all the pull requests and adding them back one by one. I think it had something to do with one PR have a target branch that was behind its source branch.
Am new to Jenkins. I found a plugin to notify the each commit status in bit bucket UI(Bit bucket Cloud Build Status Notifier Plugin) and am very much confused about notifying the build status.
https://wiki.jenkins-ci.org/display/JENKINS/Bitbucket+Cloud+Build+Status+Notifier+Plugin
Am doing commit continuously in development branch and i have registered the oauth credentials as described in above link with Jenkins job. After the Jenkins job run, i could not see the build status in bit bucket cloud UI.
Could anyone please suggest me whether this plugin update the commit status from pull request page to development branch while merge? Or This plugin can pass the direct build status to development branch when commit done and Jenkins job ran.
Thanks in advance!!!
If the plugin is configured properly you should be able to see the build status posted by the plugin in commit history of your development branch within Bitbucket Cloud. The build status is set for a given commit sha1, that means that it doesn't care if it's a pull request or not since the commit sha1 doesn't change.
If the build status is not shown in Bibucket Clould UI, I guess your problem is related to the plugin or Jenkins configuration. Take a look to the Jenkins log file for more information in order to be able to guide you to solve the problem.
I need to integrate Bitbucket with Jenkins. So that whenever a PR is opened it will trigger a build in Jenkins. Then commit status of the last commit in the PR will be updated as failed or success and this commit wont trigger the build again. (This works beautiful with Github but seems to be a nightmare for me with Bitbucket)
So far I did:
Installed Bitbucket pull request builder plugin.
Set everything up like its described in https://github.com/jenkinsci/bitbucket-pullrequest-builder-plugin#readme
User has write permissions to the repository (we added shh pub key to organization and its in the group that has write permissions)
Problems
Build is triggered over and over again for the same PR/commit
Commit status is not updated on bitbucket
Let me know if I can provide more information.
In my case, the Jenkins URL was set to http://jenkins:8080 and when such a URL was sent to BitBucket via their API, BitBucket returned the error "Invalid URL" (Look in Jenkins Logs: http://yourjenkins:8080/log/all) Which is not handled by the BitBucket Pull Request Builder plugin and thus kept continuously rebuilding all of our pull requests because it thought that build was not in progress. After setting Jenkins URL to http://jenkins.domain.tld:8080/ or http:///jenkins, the BitBucket API started accepting the URL and everything started to work.
But in your case it may be possible that some other error is the cause. You can check your Jenkins Error log to see the failure.
See the following issue: Build status notification fails with Enter a valid URL