search

mohamicorp / stash-jenkins-postreceive-webhook

Webhook used to notify Jenkins when commits are made to Stash
Other
138 stars 98 forks source link

How to debug or get logs for the plugin? #30

Closed bipingm closed 10 years ago

bipingm commented 10 years ago

Steps: 1) Configured my jenkins job to enable Polling SCM with "H 0 1 1 0". 2) Using 'curl', I can trigger my jenkins build: curl jenkins.xyz.com:8080/git/notifyCommit?url=ssh://git@stash.xyz.com:7999/eee/repo.git

But, when I enable the plugin in Stash with Jenkins URL = jenkins.xyz.com:8080 and GIT repo URL = ssh://git@stash.xyz.com:7999/eee/repo.git, merging my pull-request to the master branch does NOT trigger the jenkins build. Is there a way to look at logs for the plugin to figure out what's going on?

mikesir87 commented 10 years ago

The current deployed version of the app only logs when an exception occurred during the trigger. The next version (which I'm hoping to deploy soon) has more logging information throughout. So, until that's released, unfortunately, there isn't much to do to help.

The current released version also doesn't trigger on pull request merges. That IS in the next version. If you commit directly to a branch/master, does the trigger work?

bipingm commented 10 years ago

Thanks for your reply. Committing to master doesn't trigger the build either :( How do I check the exception logs?

mikesir87 commented 10 years ago

Hmmm... ok. The exception logs would show up in your STASH_HOME/log/atlassian-stash.log file. May want to also check your server's log file (catalina.out if running in Tomcat) just in case.

I ended up finalizing the update to the plugin yesterday and getting it released. So, go ahead and try upgrading to version 2.0. You may need to re-enable the webhook for repositories you already have it configured to use. Not sure why Stash doesn't keep it enabled. The updated version has the ability to test the configuration from the config screen without you needing to make commits/merges. If you're still having trouble, just let me know.

bipingm commented 10 years ago

It turned out to be a server port blocking issue. Thank you. I will close out this bug.