You might consider JenkinsPipelineUnit (refer to
https://issues.jenkins-ci.org/browse/JENKINS-33925 for comparisons of
various alternatives for automated testing of pipeline scripts).
If that doesn't meet your needs, could you create a test repository with
one branch per test scenario, then have i
Need to have a good dev workflow for developing share libraries my jobs depend
on.
Right now when a shared Lib is edited all jobs depending on it automatically
run. I want to control and test this code somewhat like I do with regular apps
with Jenkins.
I don't want to have to manually point my
