[DO NOT MERGE] Bump workflow-durable-task-step from 2.28 to 2.34 #82
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
As expected, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Demonstrating that jenkinsci/workflow-durable-task-step-plugin#117 fixes the problem shown in #81. Note that, like in #81, the branches of the
Jenkinsfilethat run tests in 2.164.1 are expected to fail (for the same reasons as in #81). Without write access to this repository, there is nothing I can do about this. However, the branches of theJenkinsfilethat run the tests against the version specified inpom.xml(e.g., thelinux-8branch of the pipeline) — here, 2.176.2 — are expected to pass.