-
Bug
-
Resolution: Won't Do
-
Minor
-
None
-
multibranch-action-trigger-plugin v1.8
We have one or more multibranch pipelines which uses declarative jenkinsfile to build, puch & deploy docker images.
Our wish is to do some garbage collection and delete these images and deployments when a branch/pipeline is deleted.
Depending on our branching strategy we decide if a deployment takes place and we sanitise tags to comply with docker and kubernetes naming schemes.
Because of this we assign dynamic values to the build context's environment variables/parameters and wish to pass these values to the triggered job for cleanup.
[JENKINS-61027] Add option to pass parameters/environment values from multibranch to triggered jobs
Assignee | New: Aytunc BEKEN [ aytuncbeken ] |
Resolution | New: Won't Do [ 10001 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
I thought about this, However, the way that I implemented triggering jobs do not make it possible to parse Jenkins file of multibranch job. Sorry for the inconvenience.