On Thu, Jun 25, 2015 at 09:45:10PM +0200, Mikolaj Izdebski wrote: > As briefly discussed today during the meeting, I would like to evaluate > the possibility to use our packaged Jenkins in Fedora infrastructure, > instead of upstream binaries. (Jenkins is available[1] in Fedora 21 and > later.) > > To get started with development of new Jenkins machines I would need > someone to create 2 new cloud machines: master with Fedora 22 and with > any OS (RHEL 6 would be my choice), each machine with at least 1 CPU, 2 > GB RAM, public IP and root access for me (FAS: mizdebsk). > > From that I will try to come with my proof-of-concept of "the new > Jenkins". If people like it then old data can be migrated and it can > become the new production instance. If not we can just scratch these > machines and keep using upstream binaries. > > So if you don't mind I'd start working on this. > Should I open a ticket for creating the new cloud instances? > > Some more technical notes: > > 1) It is possible to use third-party plugins with packaged Jenkins, > which means that missing plugins can be installed as binary blobs until > they are packaged in Fedora. > > 2) Jenkins RPMs must be installed only on master node. All slave nodes > can connect to master and download Jenkins code from there. Slaves still > need to have basic environment installed (such as Java, git, mock), but > not Jenkins itself. This means that only the master node must be Fedora > 21+, slaves can be anything (RHEL 6/7, older Fedoras). > > 3) Michal Srb is currently looking into packaging Jenkins as software > collection for RHEL 6 and 7. Once (and if) done this could allow having > RHEL 7 master, with the disadvantage of using "unofficial" RPMs from > softwarecollections.org. This is just the beginning and we can evaluate > having non-Fedora master later, if needed. > > [1] https://fedoraproject.org/wiki/Changes/Jenkins This sounds all quite nice, thanks for picking it up! Just a side question, if we were to use an EL for the master node, is there an advantage of using SCLs over using upstream's repo as we do now? Otherwise, +1 on the Fedora master and let me know if I can help. We would probably have to re-adjust the jenkins playbook, likely in something like: roles/jenkins/{master,slaves} instead of the big blob we currently have. Pierre _______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure
