Skip to content

Revert "Bump org.jenkins-ci.plugins.workflow:workflow-step-api in /bo…#2846

Merged
basil merged 3 commits intomasterfrom
fix/revert-workflow-step-api-657
Jan 19, 2024
Merged

Revert "Bump org.jenkins-ci.plugins.workflow:workflow-step-api in /bo…#2846
basil merged 3 commits intomasterfrom
fix/revert-workflow-step-api-657

Conversation

@alecharp
Copy link
Member

@alecharp alecharp commented Jan 19, 2024

…m-weekly (#2845)"

This reverts commit 6b58cd0.

Testing done

Running local-test script locally with PLUGINS=credentials-binding.
This because I detected a problem on the release preparation work. Doing a bisect showed that the problem was the version bump of workflow-step-api. Additional research showed that the problem came from jenkinsci/workflow-step-api-plugin#143.

Initial error report can be seen here: https://ci.jenkins.io/job/Tools/job/bom/job/master/2425/pipeline-console/

cc @jglick

The problem can be reproduced outside of the BOM by running mvn clean verify -Dtest=org.jenkinsci.plugins.credentialsbinding.impl.BindingStepTest#widerRequiredContext on credentials-binding. The pull request on workflow-step-api changed the wording of the context error but that was not updated in the credentials-binding test.

### Submitter checklist
- [x] Make sure you are opening from a **topic/feature/bugfix branch** (right side) and not your main branch!
- [x] Ensure that the pull request title represents the desired changelog entry
- [x] Please describe what you did
- [x] Link to relevant issues in GitHub or Jira
- [x] Link to relevant pull requests, esp. upstream and downstream changes
- [x] Ensure you have provided tests - that demonstrates feature works or fixes the issue

@alecharp alecharp requested a review from a team as a code owner January 19, 2024 16:11
@basil basil merged commit b92a39d into master Jan 19, 2024
@basil basil deleted the fix/revert-workflow-step-api-657 branch January 19, 2024 16:39
@basil
Copy link
Member

basil commented Jan 19, 2024

If jenkinsci/credentials-binding-plugin#287 isn't merged and released in a short timeframe, please file a BOM issue to track the removal of this workaround. (No need for the formality if the fix is imminent, but want to keep us from losing track if the fix takes longer.)

@jglick
Copy link
Member

jglick commented Jan 19, 2024

#2848

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants