4 ms·

Yeah, version control of Jenkins itself has always scared me. There seems to be a pattern that we go through. (in the beginning, there was light...) * Create

Yeah, version control of Jenkins itself has always scared me. There seems to be a pattern that we go through. (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.

wahnfrieden 11y ago
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). https://github.com/jenkinsci/job-dsl-plugin https://github.com/jenkinsci/job-dsl-plugin
- gnoway 11y ago
  We're using this as well, it's got warts but it's 100x better than authoring jobs in the web ui.
- mikehollinger 11y ago
  Apache Bigtop relies on this, and does a pretty spiffy job of configuring itself out of the box this way. Will look more closely...
- loevborg 11y ago
  I use http://docs.openstack.org/infra/jenkins-job-builder/ http://docs.openstack.org/infra/jenkins-job-builder/, which is great as well: Jenkins configuration in a simple YAML file under source control.
jacques_chester 11y ago
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.
zwischenzug 11y ago
I mentioned this elsewhere in the thread, but here goes: https://zwischenzugs.wordpress.com/2016/01/24/ci-as-code-stateless-jenkins-deployments-using-docker/ https://zwischenzugs.wordpress.com/2016/01/24/ci-as-code-sta... https://zwischenzugs.wordpress.com/2016/01/30/ci-as-code-part-ii-stateless-jenkins-with-dynamic-docker-slaves/ https://zwischenzugs.wordpress.com/2016/01/30/ci-as-code-par... https://zwischenzugs.wordpress.com/2016/02/25/922/ https://zwischenzugs.wordpress.com/2016/02/25/922/
PascalW 11y ago
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. [1] https://github.com/kabisa/jenkins-docker https://github.com/kabisa/jenkins-docker

wahnfrieden 11y ago

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). https://github.com/jenkinsci/job-dsl-plugin https://github.com/jenkinsci/job-dsl-plugin

gnoway 11y ago
We're using this as well, it's got warts but it's 100x better than authoring jobs in the web ui.
mikehollinger 11y ago
Apache Bigtop relies on this, and does a pretty spiffy job of configuring itself out of the box this way. Will look more closely...
loevborg 11y ago
I use http://docs.openstack.org/infra/jenkins-job-builder/ http://docs.openstack.org/infra/jenkins-job-builder/, which is great as well: Jenkins configuration in a simple YAML file under source control.

jacques_chester 11y ago

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.

zwischenzug 11y ago

I mentioned this elsewhere in the thread, but here goes: https://zwischenzugs.wordpress.com/2016/01/24/ci-as-code-stateless-jenkins-deployments-using-docker/ https://zwischenzugs.wordpress.com/2016/01/24/ci-as-code-sta... https://zwischenzugs.wordpress.com/2016/01/30/ci-as-code-part-ii-stateless-jenkins-with-dynamic-docker-slaves/ https://zwischenzugs.wordpress.com/2016/01/30/ci-as-code-par... https://zwischenzugs.wordpress.com/2016/02/25/922/ https://zwischenzugs.wordpress.com/2016/02/25/922/

PascalW 11y ago

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. [1] https://github.com/kabisa/jenkins-docker https://github.com/kabisa/jenkins-docker