Description:
In original Bitbucket repository, we configured a 'Webhook to Jenkins for Bitbucket Server' using 'Git plugin'. Every new pull request (from feature branch or forked repository) will trigger Jenkins job which has '+refs/pull-requests/*/from:refs/remotes/*' as 'Refspec' and '**/pull-requests/**' as 'Branches to build'.
PR's are updated by pushing commits to feature branch in original repo or forked repository.
Expected behavior:
New commits (PR updates) will trigger pipeline.
Actual behavior:
Commits from original repo branch triggers pipeline.
Commits from forked repository do not triggers pipeline.
Thank you for sharing your findings on this matter.
We already have a feature request reporting this:
Please make sure you vote and watch it. Our project managers will prioritize it according to our Features Policy.
Thx Daniel for the answer.
Best regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You are welcome! =]
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.