Can I access the real "dir", "sh" etc. in my pipeline? about jenkinspipelineunit HOT 6 CLOSED

Hey, I spun up a repository that is for integration testing Jenkins versions + plugins + shared libraries for this exact issue: https://github.com/SpencerMalone/JenkinsPipelineIntegration

from jenkinspipelineunit.

Hi @RudolfVonKrugstein,

Sorry for the late response.

The testing framework has no knowledge of real implementations of these steps.

So you should write your own mock implementations that execute steps. But it'll be laborious,
there are a plethora of kinds of steps. If you want to mock a small subset, I guess it is manageable but you should mock also the workspace (execution directory), scm steps, sh, dir etc.

from jenkinspipelineunit.

Ok, thanks. For now I will mock according to my needs, which leaves most things unmocked :-).

from jenkinspipelineunit.

Great! Is there a reason why you cannot use version 1.0 of this framework ?

from jenkinspipelineunit.

from jenkinspipelineunit.

Indeed I looked more into it. You do not use the unit testing at all.
The JenkinsRule approach is totally viable to test if a shared library is compatible with a given version of jenkins and plugins.

The startup times you are getting should be higher though.
It would be great to find some middle ground and get both the practicality of this fw with the high reliability of JenkinsRule.

from jenkinspipelineunit.