I agree with this answer. With a pipeline, it is so easy to make logic
decisions and much easier to maintain a single Jenkinsfile that has all the
logic. There is surely going to be some duplicated logic, so now only the
special differences have to be handled, and you don't duplicate code
I think the most common solution is to have one Jenkinsfile (per branch),
and manage everything from that.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
I think you can have a "build" variable
(https://jenkins.io/doc/pipeline/tour/environment/), or parameter (below),
and use the value assigned to that.
Using parameters in a Jenkinsfile. When this runs you will get an
interactive window.
pipeline {
agent any
parameters {
Hi,
I am new to Github. I am trying to use the Github Organization Plugin to set
up my pipelines in Jenkins.
I am able to get the corresponding pipelines per branch in Jenkins. What I
do want to do is to set up multiple pipelines based off multiple JenkinsFile
in one branch.
For eg. I would have a
