Details
-
Bug
-
Resolution: Invalid
-
Low
Description
Hello,
I am trying to setup a Jenkins job as a post-commit Service for my Bitbucket repo. Trying to use the standard Jenkins service, that was never executing. I finally gave up and tried a standard post service with the following URL (pw obscured):
https://lsi%40liquidation.com:8154314@lsi.ci.cloudbees.com/job/GitRef2Dev/build?token=tkn
When running "curl -O
{same URL}" from command line, my Jenkins job kicks off right away, but no pushes to master on that repo in Bitbucket show any reaction to Jenkins. What could be the difference here? Jenkins URL is accessible from URL as it's running in the cloud.