Jenkins update

[Pierre-Yves Chibon]

Hi all,

I have written this last week-end and I'm late...

I have started to write down some instruction on how one can get his/her
project added to our jenkins server:
https://fedoraproject.org/wiki/Jenkins@infra

And (attached) I wrote a small SOP on how we should handle this.

These two documents are up for review, discussion and correction.

Please fire away :)
Thanks,
Pierre

-------------- next part --------------
= Jenkins =

Jenkins is a continuous integration server which we are hosting in the Fedora infrastructure cloud.

== Set-up ==

The systems are set-up using ansible in the following way
* We have on jenkins master
** the master does not run jobs
** the master can send emails
** the master can be accessed from the outside by http(s)
** the jenkins configuration is backed-up on the master

* We have jenkins slaves
** the slaves are just 'building' hosts, they are the ones that run the jobs
** the master connects to the slave via ssh
** the slaves are throw-away VMs - at any time they can be rebuilt

== Add a project to jenkins ==

The procedure is as follow:
* user makes a request on the fedora infrastructure trac
* admin sees request
* admin checks quickly the project
* if al seems fine, admin create the project on jenkins:
** go to https://jenkins.cloud.fedoraproject.org
** login (uses fas-openid)
** go to 'New job' ( http://jenkins.cloud.fedoraproject.org/view/All/newJob )
*** set the name as provided in the ticket
*** use by default: "Build a free-style software project" as project type
** you end up on the configure page of the project:
*** set the description as given in the ticket
*** Check the box "Enable project-based security"
*** add the user given in the ticket to the ACL matrix
*** give this user all permission (for this project)
*** to the "Anonymous" user give the ACL: "read" in the "Job" category

Done :)