Subject: CAcert Code Development list.
List archive
- From: Jan Dittberner <jandd AT cacert.org>
- To: cacert-policy AT lists.cacert.org
- Cc: Eva Stöwe <eva.stoewe AT cacert.org>, Martin Gummi <martin.gummi AT cacert.org>, Benny Baumann <benbe AT cacert.org>, Felix Dörre <felix AT dogcraft.de>, cacert-devel AT lists.cacert.org
- Subject: Jenkins setup for great good :-)
- Date: Thu, 5 Feb 2015 16:34:34 +0100
Hello,
I setup a Jenkins [1] instance [2] that can be used for building policy
documents and perform other automated tasks (CCing cacert-devel to make the
developers aware). The first job of Jenkins is a build job for the policy
build tool by Felix Dörre [3] that was created in parallel to my previous
idea with Sphinxdoc and makes plain text policies even easier.
[1] http://jenkins-ci.org/
[2] https://jenkins.cacert.org/
[3] https://jenkins.cacert.org/job/cacert-policy-parser/
I added Martin and Benny as Jenkins admins and created an account for Eva
too (you get initial account information via private mail). I setup Jenkins
to allow new user registrations [4] so that all interested people can get
read access. When you need more permissions you can just send a mail to
jenkins-admin AT cacert.org.
[4] https://jenkins.cacert.org/signup
The next step should be to define the workflow that we want to build there.
My idea is something like this:
1.) Manage the policy source text files in either SVN or Git (should be
decided by the people that will work on the policy texts)
2.) Create a Job that looks for changes in the repository from step 1 and
builds the HTML representation with Felix' tool
Jenkins allows viewing of the build results in a browser so this might
be sufficient for snapshots of the generated policy documents.
3.) Setup an additional Jenkins job that allows a one (or two) click
publication of a chosen policy document to the target (to be decided
but my impression is that git publication to a separate subdomain like
policies.cacert.org on webstatic would be easy). That Jenkins job would
be the official "ceremony" to publish policies and should be executed by
the policy officer.
Do you agree with this idea and should I / we continue with such a setup?
Best regards
Jan
--
Jan Dittberner - CAcert Infrastructure Team
Software Architect, Debian Developer
GPG-key: 4096R/558FB8DD 2009-05-10
B2FF 1D95 CE8F 7A22 DF4C F09B A73E 0055 558F B8DD
https://jan.dittberner.info/
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
- Jenkins setup for great good :-), Jan Dittberner, 02/05/2015
- Re: Jenkins setup for great good :-), Benny Baumann, 02/06/2015
- Re: Jenkins setup for great good :-), Ian G, 02/06/2015
- Re: Jenkins setup for great good :-), Alex Robertson, 02/06/2015
Archive powered by MHonArc 2.6.18.