This repository has been archived by the owner on Jan 18, 2020. It is now read-only.
[JENKINS-51731] Running a standalone Pipeline should be feasible out of the box #101
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
JENKINS-51731
Discovered as I was trying to use a simple standalone pipeline during a demo today, when not installing any additional plugin with the wizard.
In my previous testing I had used freestyle jobs 🤦♂️...
Even if we will anyway totally rewrire this part, this seems like an acceptably small and easy short term fix.
Manually tested using
make runfor now.Once I complete JENKINS-49866, I will add an automated test to check this keeps working.