<XL> are my comments below.
--
Xavier.t Lamien
--
http://fedoraproject.org/wiki/XavierLamien
GPG-Key ID: F3903DEB
Fingerprint: 0F2A 7A17 0F1B 82EE FCBF 1F51 76B7 A28D F390 3DEB
On Wed, Mar 6, 2013 at 11:32 PM, Pierre-Yves Chibon <pingou@xxxxxxxxxxxx> wrote:
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
== How can I add my project to Jenkins? ==
[..snip]
<XL>
You can actually add this as a template so people can just fill up the form.
Look at ticket type in admin panel if you have access to.
[...] meaning you have to take care of specifying the dependencies (or in some case, ask fedora-infrastructure to add them to the builders).
<XL>
How does that work here?
I mean, is people allow to install packages from build-step - or - will it have specific amount of images with required packages requested from people?
Also, as job's owner has full access to it's job, is there any policy regarding the build trigger (which requires to set a token) option?
And how many jobs an instance can run? I see only 2 per instance for now, can an instance have more than that?
And (attached) I wrote a small SOP on how we should handle this.
"** the master connects to the slave via ssh"
<XL>
Any technical reason for this one?
Why not use the excellent swarm plugin which allows slaves to auto-discover to jenkins master?
So we can pre-package an image with the swarm client, run the instance, instance gets up and automatically join in (look for master from UDP, found it and start hand-shake stuff), gives it's resources availability
and start jobs once master load-balance build.
This have the advantage of add/remove slaves without explicitly adding/removing nodes from the setting panel.
(e.g the 2 slaves are pretty busy and you need a build in the queue to be done asap, you fire an instance up and master send your build to it.)
"Add project to jenkins"
<XL>
Jenkins provides some useful remote access API which can help you do this part easier.
You can even ansible it ;)
If you have time you can also use their python API to write a jenkins-job-setup.py <option>
So admin can just log in to lockbox and ansible or jenkins-job-setup.py .
Maybe you should look at it.
These two documents are up for review, discussion and correction.
Please fire away :)
Thanks,
Pierre
_______________________________________________
infrastructure mailing list
infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Xavier.t Lamien
--
http://fedoraproject.org/wiki/XavierLamien
GPG-Key ID: F3903DEB
Fingerprint: 0F2A 7A17 0F1B 82EE FCBF 1F51 76B7 A28D F390 3DEB
_______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure
