Open ctataryn opened 7 years ago
I've encountered a problem with 'unconfigured-jenkins-location' when trying to reach the jenkins build from bitbucket pull request. The URL pointed to http://unconfigured-jenkins-location/... , while the 'Jenkins location' in the jenkins configuration was supplied correctly.
Maybe because the bitbucket-branch-source-plugin was installed áfter the 'Jenkins location' was specified in the jenkins configuration, the URL was not set in the plugin configuration. After altering the jenkins location and then changing it back to the correct URL, the issue was resolved. Now bitbucket receives the correct url to jenkins for pull request builds. This imo confirms the workaround decribed above.
I also have this issue.
If you leave your Jenkins URL pointing at
localhost
underManage Jenkins->Configure System->Jenkins Location->Jenkins URL
when an api call is made bycom.cloudbees.jenkins.plugins.bitbucket.client.BitBucketCloudApiAdapter
for:It will fail with the error:
The reason for this is when you leave your Jenkins URL configured for localhost, somewhere along the way the URL is replaced with
http://unconfigured-jenkins-location/...
When this is passed into the POST body like so:The BitBucket API will complain with the aforementioned error.
WORKAROUND: If you go in and just change the Jenkins URL, everything works right. Even if you change the Jenkins URL back to
localhost
it's enough just so that field is dirtied and then written to the configuration.