-
Notifications
You must be signed in to change notification settings - Fork 353
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jenkins Custom checkout fails for PR jobs #819
Comments
I'm experiencing the exact same issue. PR checkout worked on version 848.v42c6a_317eda_e. Tried to find solutions but ended up with a rollback to 848.v42c6a_317eda_e. This issue is highly relevant and active. |
Same here, had to revert to Bitbucket Source plugin, with version 877 I get
and then
|
Same on our builds after upgrading from 866 to 874. Behavior of env.BRANCH_NAME was changed I think. |
Same here, |
Indeed #796 appears to have broken quite a few things. We use quite a lot of logic relating to git-flow, so we use stuff like:
Which no longer works, since there is no To be fair: the But these were breaking changes nonetheless. I guess with the new plugin version, it would be something like:
|
Semi-related note that the lack of a |
@andrey-fomin can you take a look if your changes are the issue here please? |
regular PR' building is broken for us too, that gets introduced by [871.v28d74e8b_4226], which happens to also be a security fix: https://www.jenkins.io/security/advisory/2024-03-06/#SECURITY-3300 |
The problem is still relevant |
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
LINUX
Reproduction steps
Expected Results
Checkout should happen for normal branches and PR branches in jenkins pipeline.
Actual Results
Jenkins job fails with below error for PR branch jobs in jenkins. However the feature branch jobs continue to work
ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.
Anything else?
Checkout happened without any issues for PR branch jobs until we upgraded the bitbucket branch source plugin from 866.vdea_7dcd3008e to 876.v857269a_5f439
Are you interested in contributing a fix?
No response
The text was updated successfully, but these errors were encountered: