I went back and forth on this. In the end, I put everything in code. I
decided I wanted the minimum amount of stuff configured in jenkins.
I started out with a wrapper pipeline that loaded the "guts" of the job.
This was extremely restrictive in that each job had to conform at some
level to th
Hi everybody,
Since a lot of my jobs have more or less the same set of parameters, I
wanted to implement a "parent job" where we have the shared configuration,
and all "children" jobs should just inherit from the "parent" and change
the parameters if needed.
I have found that the "inheritance
=wYi3JgyN7Xg
Feel free to check it out, try it out and give us some feedback on it.
Best regards,
Norman
--
View this message in context:
http://jenkins-ci.361315.n4.nabble.com/Job-Inheritance-tp4653700p4674346.html
Sent from the Jenkins users mailing list archive at Nabble.com.
--
You received
I found a reply by @stussy saying he was using the beta of the Planned
Parenthood plugin. Does anyone know where to get that plugin?
http://jenkins.361315.n4.nabble.com/Job-Inheritance-td4653700.html
http://www.cloudbees.com/jenkins-user-conference-2012-san-francisco.cb
--
You received this
drawback in Jenkins which is solved in Hudson: job
> inheritance. In other words, the funcionality of defining common
> configuration in a parent job and apply to its children. In our case this
> is a necesarry feature, because we need to manage 300 projects at least.
>
> I
Hi,
I'm considering Jenkins as continuous integration tool in the company where
I work. I prefer Jenkins than Hudson because I believe it has a better
future and it's widely adopted.
However, I've seen a drawback in Jenkins which is solved in Hudson: job
inheritance. In o
