We can run existing jobs in the pipeline script:
if we do use the build “jobname” feature of the pipeline, we lose some of the pipeline functionality with using the other plugins as they run in a different space from the build “jobname” (for example cannot use the stash feature to pass on the artifacts to another job/stage)
My question then is - can I with existing jobs, orchestrated by pipeline as you write, pass artifacts to downstream some other way than the "stash feature" of pipeline?
Usually I would use copy artifacts, fingerprinting and pass down buildnumber from upstream to downstream, so downstream can copy the correct artifact.
Is that possible?
In #28 you wrote:
My question then is - can I with existing jobs, orchestrated by pipeline as you write, pass artifacts to downstream some other way than the "stash feature" of pipeline? Usually I would use copy artifacts, fingerprinting and pass down buildnumber from upstream to downstream, so downstream can copy the correct artifact. Is that possible?
You need two jobs to test it.