Hello all,
at the department I am working at we operate a Jenkins with ~100 pipeline
jobs.
The jobs have evolved over ~4 years without any conventions about job and
stage names.
Today we have a mess. Related jobs cannot easily be recognized by name. The
"logic" how a job is sectioned into stages
I have multiple pipelines written in groovy that call a job.
I need to pass the upstream job name to a downstream job, and I'd like to
do so without modifying every pipeline by sending the parametized job name
environment variable to the job.
I'm trying to find a way to do so from the downstream
Am Mittwoch, den 27.01.2021, 08:53 -0800 schrieb 'Martin Schmude' via
Jenkins Users:
> Any hints?
While I won't tell you how to name your jobs, I'd like to point you at
the folders plugin, which might help to organize them better.
HTH...
Dirk
--
Dirk HeinrichsSenior Systems Engineer, Delivery