We recently upgraded to 3.11.0 from an older 2.x version and now our jenkins build triggers are not firing on commit. We are using the "web hooks for jenkins" plugin http://nerdwin15.com/2013/04/continuous-integration-with-stash-and-jenkins/ Testing from within the configuration works fine. I don't see any info about the commits working or not in the stash logs and no network traffic of any kind between stash and jenkins after a commit or merge. I do see the traffic when testing.
I did find the correct logs where I can see some activitiy and i enabled debugging. This got me the below error:
2015-08-06 15:45:04,266 ERROR [JenkinsWebhook:thread-11] @13W8V84x945x4990x0 1bwc3m3 192.168.1.100 SSH - git-receive-pack '/poc/test.git' com.nerdwin15.stash.webhook.Notifier Error getting Jenkins URL
java.lang.IllegalStateException: There were no SSH clone links generated for repository POC/test
at com.atlassian.stash.internal.ssh.service.DefaultSshCloneUrlResolver.getCloneUrl(DefaultSshCloneUrlResolver.java:37) ~[na:na]
at com.nerdwin15.stash.webhook.Notifier$2.perform(Notifier.java:258) ~[plugin.189253547604078990.stash-webhook-jenkins-2.7.0_1438016135000.jar:na]
at com.nerdwin15.stash.webhook.Notifier$2.perform(Notifier.java:255) ~[plugin.189253547604078990.stash-webhook-jenkins-2.7.0_1438016135000.jar:na]
at com.atlassian.stash.internal.user.DefaultEscalatedSecurityContext.call(DefaultEscalatedSecurityContext.java:51) ~[stash-service-impl-3.11.0.jar:na]
at com.atlassian.stash.internal.user.DefaultSecurityService.doWithPermission(DefaultSecurityService.java:77) ~[stash-service-impl-3.11.0.jar:na]
at com.nerdwin15.stash.webhook.Notifier.getUrl(Notifier.java:255) [plugin.189253547604078990.stash-webhook-jenkins-2.7.0_1438016135000.jar:na]
at com.nerdwin15.stash.webhook.Notifier.notify(Notifier.java:196) [plugin.189253547604078990.stash-webhook-jenkins-2.7.0_1438016135000.jar:na]
at com.nerdwin15.stash.webhook.Notifier.notify(Notifier.java:165) [plugin.189253547604078990.stash-webhook-jenkins-2.7.0_1438016135000.jar:na]
at com.nerdwin15.stash.webhook.Notifier$1.call(Notifier.java:144) [plugin.189253547604078990.stash-webhook-jenkins-2.7.0_1438016135000.jar:na]
at com.nerdwin15.stash.webhook.Notifier$1.call(Notifier.java:141) [plugin.189253547604078990.stash-webhook-jenkins-2.7.0_1438016135000.jar:na]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_40]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_40]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_40]
... 43 frames trimmed
Sorry to hear you're having trouble with your Jenkins hooks. The error you're seeing is caused by a bug in Stash 3.11.0 itself, for which a fix is currently in review and will be released shortly. For more details, keep an eye on this ticket: https://jira.atlassian.com/browse/BSERV-7827
Norman Ma (Atlassian)
I had a couple of issues with that hook after I upgraded my Stash to 3.9.1. Take a look at: https://github.com/Nerdwin15/stash-jenkins-postreceive-webhook/issues/141 https://github.com/Nerdwin15/stash-jenkins-postreceive-webhook/issues/140
This is so irritating. I don't want to stop using Stash because of this. But, I'm beginning to wonder if we made the wrong decision to use Stash instead of github. We like having the servers in-house. But, if atlassian is sabotaging plugins that help people use non-atlassian products, that is pretty scary.
It's a free plugin, if there are changes to Stash, the plugin must adapt to it and it's the owner's responsibility and/or anyone's. Good thing that the code is publicly hosted in github, so anyone can suggest fixes and submit it to the owner if he/she don't have the time for it.
Good point. The plugin owner gets very little out of fixing this. Atlassian, on the other hand, will lose customers if it is not fixed. Perhaps Atlassian should consider bringing this plugin in-house. Or, at the least, submitting a pull request with a fix and begging/paying the plugin owner to accept it.
On the plugin site under issue https://github.com/Nerdwin15/stash-jenkins-postreceive-webhook/issues/133 there is a work around posted: @mikesir87 I did a test: changed the "Repo Clone URL" from "SSH" to "CUSTOM" and specified the exact same (ssh) url. And it worked!
Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs