webhook firing on manual trigger but not push

Joe Schrag December 28, 2015

I have a system which has been happily running Stash with the Jenkins Webhook plugin for quite a while.  I recently installed the Sonar plugin and started to experience problems.  The Jenkins job no longer gets triggered by a push.  However, a user can trigger a build manually by using the "Trigger Build" button if the branch has an open pull request.

One relevant detail is the fact that the instructions for configuring the Sonar plugin recommended checking the "Omit SHA1 Hash Code" setting on your repo.  I have since reverted that setting and uninstalled the Sonar plugin, but the problem persists.

Anyone have an idea of what might be going on?

1 answer

1 accepted

0 votes
Answer accepted
Joe Schrag January 5, 2016

I finally found the problem in a log file I had missed.  There was an entry containing this error:

com.nerdwin15.stash.webhook.Notifier Error getting Jenkins URL
org.springframework.osgi.service.importer.ServiceProxyDestroyedException: service proxy has been destroyed

 

I found a somewhat similar problem here: 

https://answers.atlassian.com/questions/23765505

and the solution therein worked for me as well

changed the "Repo Clone URL" from "SSH" to "CUSTOM" and specified the exact same (ssh) url.

 

 

 

 

 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events