For months now, I and the local Jenkins admins I work with, have been 
struggling with a problem where my main jenkins job is not firing on a 
"notifyCommit" firing from a BitBucket instance.  We actually were able to 
define another job in the same Jenkins instance, pointing to the same repo, 
that IS fired when the notifyCommit url is hit, but we still can't get the 
normal job to fire.  We also see the log entry that shows the notifyCommit 
call, but it just doesn't start the job.

The job works fine when we run it manually, it just doesn't fire 
automatically.  It also works fine when it's spawned from the 
"buildWithParameters" URL, which we use to build pull request branches 
automatically (the same job is designed to build both master and pr 
branches).

We've tried numerous variations of the value in the "Branches to build" 
field, but it doesn't appear to make any difference.

We're using v2.46.2 of Jenkins and v3.3.0 of the git plugin for Jenkins.

Assuming no one here has any bright ideas about why this is happening, I 
figure my next step is to connect to the Jenkins instance with a remote 
debugger and step through the code.  In order to do that, I have to obtain 
the correct code to step through, and some hints on some breakpoints to set.

I figure I at least need the source for the correct release.  When I look 
on github, I see a release for "2.46.3", but not "2.46.2".  I do see that 
github has a "3.3.0" release for the git plugin, so I assume I'm ok there.

Assuming I can get the 2.46.2 vs. 2.46.3 issue resolved, are there any 
other plugins that I need to get the source for in order to properly debug 
this?

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/37353cbf-b2d3-4afd-8730-229f952b3e38%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to