I have been tasked to look at how we can set up a self service CI system
for a large development shop, much along the lines of how travis CI works.
There are big differences between what we need and what Travis CI provides
but the basic idea of having a yaml file within the repository itself
specify what the build server should do is what we are aiming for.
Jenkins-Job-Builder from OpenStack seems to provide what we need from the
standpoint of being able to take yaml files and create Jenkins jobs from
them. The part that I am seeking advice on is how to make this work from
within a job, specifically we are looking for a workflow something like
this:
- Given a job that is configured with an SCM Poll to poll a given git
repository.
- When that poll triggers.
- Get the latest source
- Evaluate the build.yml file to create the rest of the jenkins job
to executed
- Execute the rest of the build job.
We have a working prototype right now that manages this with two separate
jobs. One to watch the SMC and rebuild the downstream job based on the
build.yml and a separate downstream job that kicks off when the first
completes successfully. (Given the first might fail if the yaml files is
invalid, etc.) The problem with this approach is that we have hundreds of
builds already, doubling the number of builds as this approach will do, is
not considered acceptable.
Any advice or thoughts on what might be the best approach to doing this
will be greatly appreciated.
--Ken
--
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/ee6fb65b-c851-444b-b481-67d390b4b371%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
