For several years, we have been using Stash to manage our Git repos. The host name for our server was 'stash.xxx.com'.
Recently we upgraded to the latest version of Bitbucket Server. At the same time, we upgraded the server hardware, and to avoid confusion that might occur when users connected to 'stash.xxx.com' and landed in 'Bitbucket Server', we set the host name as 'bitbucket.xxx.com'. We also configured Bitbucket Server to use a base URL of 'http://bitbucket.xxx.com'. This had the adverse effect of breaking the Stash Webhook to Jenkins in that the URL used in the notifyCommit no longer matches any of the jobs in Jenkins. ex. http://jenkins.host.com/git/notifyCommit?url=http://bitbucket.xxx.com/.... no longer matches any of the jobs that are configured to fetch from http://stash.xxx.com/... and we no longer have builds kicked off when code is pushed to Bitbucket Server. Maybe it was a mistake to change the base url for Bitbucket Server, but 'bitbucket' seemed more appropriate than 'stash' for access to the UI. Suggestion: To deal with this situation, it would be handy if the Git plugin provided a means to configure host name aliases so that the notifyCommit message would trigger polling for 'stash.xxx.com' or 'bitbucket.xxx.com'. Would this be of general interest? Michael Giroux -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/7a78e256-8945-412d-84d3-0f37cea6c6be%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
