Open RecuencoJones opened 3 years ago
Well, one thing is running a Pipeline in a real jenkins, that uses a shared library. The other thing is running some unit and/or integrationTests of a shared library.
running ./gradlew test like JenkinsPipelineUnit suggests will give you a "mocked", kind of like "simulated" jenkins execution environment. It is meant to test tiny pieces (unit) of your shared library for proper execution.
For example if you want to make the steps from your shared library available you will have to follow the examples provided in order to load the code (or maybe some mocks to abstract real execution stuff).
Be assured that I consider myself a novice on groovy, testing and jenkinsPipelineUnit. Currently I just try to pave my way through alle these problems myself, so I could well just be plain wrong. ;)
Version report
Reproduction steps
./gradlew test
Results
Expected result:
Successful execution as in Jenkins (check sample execution logs below)
Actual result: