Re:Jenkins 2.0 Beta
by wahnfrieden on Friday March 25, 2016 @04:49PM
(#11362582)
We use Netflix's Job-DSL to keep Jenkins job configuration in source control (and to allow easier reuse than offered with job reuse plugins).
I use http://docs.openstack.org/infra/jenkins-job-builder/, which is great as well: Jenkins configuration in a simple YAML file under source control.
Re:Jenkins 2.0 Beta
by mikehollinger on Friday March 25, 2016 @06:07PM
(#11363054)
Apache Bigtop relies on this, and does a pretty spiffy job of configuring itself out of the box this way.
Will look more closely...
We're using this as well, it's got warts but it's 100x better than authoring jobs in the web ui.
At my work we're running all Jenkins jobs in Docker containers using some simple scripting [1].
Works really great. Jobs can run on any slave, no snowflakes, full CI config is versioned in the repo along with the code. Jenkins job only point to a single script and that's it.
Re:Jenkins 2.0 Beta
by zwischenzug on Friday March 25, 2016 @04:54PM
(#11362612)
I mentioned this elsewhere in the thread, but here goes:
https://zwischenzugs.wordpress.com/2016/01/24/ci-as-code-sta... https://zwischenzugs.wordpress.com/2016/01/30/ci-as-code-par... https://zwischenzugs.wordpress.com/2016/02/25/922/
Re:Jenkins 2.0 Beta
by jacques_chester on Friday March 25, 2016 @04:31PM
(#11362466)
I think you would find Concourse to be a very appealing alternative; out of the box it gets you a lot closer to reproducibility than Jenkins does.
(in the beginning, there was light...)
* Create a small, tight, single-purpose Jenkins job
* Add a small tweak to it
(repeat adding tweaks)
(realize the Jenkins job now contains MANY different configurations options and the job itself is now a shell script in its own right)
* Sweep the "job" into a shell script. Check in said shell script
* Back up the Jenkins config, and hope no one asks why something's happened.
I now have a plugin that automatically checks in the Jenkins config to source control, but it again doesn't solve the problem of matching up a particular jenkins artifact to exactly what built it, and why.