We use Jenkins RPMs on Fedora and Scientific Linux (similar to CentOS) here. The experience has been fine.
However, at some point I decided to grab the https://github.com/jenkinsci/packaging.git RPM creation project and customise the Jenkins RPM for our site. e.g. increase the memory allocation for the Java process and change the JENKINS_HOME, since we run a rather big Jenkins instance. This has also made my life easier when dealing with IT, who have little understanding of the configuration adjustments needed specifically for our Jenkins instance. ________________________________________ From: [email protected] <[email protected]> on behalf of Jason LeMauk <[email protected]> Sent: 11 July 2017 16:37:18 To: [email protected] Subject: RE: Installing / maintaining Jenkins on a Linux host machine Thank you for sharing your experience! The company is leaning towards not using Ubuntu / Debian, however we can still use it as our native operating system hosting our Jenkins instance if it is best practice / required. I have my own personal Jenkins instance setup on an Ubuntu machine and agree that the Ubuntu approach has been pretty straight forward. Does anybody have any experience installing / maintaining Jenkins on a non-Debian / non-Ubuntu Linux operating system (with Red Hat / Fedora / CentOS ruled out)? I am trying to discern whether or not we are relegated to a Debian / Ubuntu base operating system to host our Jenkins instance on (keeping in mind that Red Hat / Fedora / CentOS is ruled out). It should probably be noted that we will likely install / upgrade on the Jenkins LTS release schedule. Thanks again for any advice or guidance! - Jason From: [email protected] [mailto:[email protected]] On Behalf Of Peter Berghold Sent: Tuesday, July 11, 2017 10:28 AM To: [email protected] Subject: Re: Installing / maintaining Jenkins on a Linux host machine I migrated my Jenkins installation over to Ubuntu from RHEL and haven't looked back. My drivers may be different than yours and my reason was I am using Jenkins to perform CI on my Puppet environment. Part of that is running some tests on the Puppet code before it is deployed and this works *much* better on Ubuntu that Red Hat which was getting rather McGiverish given all the hacks I did to get it to work. So I guess YMMV depending on what you are trying to accomplish. If you are doing this in a corporate environment make sure with the powers that be whatever solution you pick meets with your list of acceptable solutions. On Tue, Jul 11, 2017 at 10:18 AM Jason LeMauk <[email protected]<mailto:[email protected]>> wrote: We are currently provisioning a physical server as our automation server. We are making considerations as far as what our native operating system should be on this physical machine. We are going to use a Linux OS as our operating system. From the Jenkins download page, https://jenkins.io/download/, I can see that Jenkins’ package distribution is available to Red Hat / Fedora / CentOS (which we will not be using), as well as Ubuntu / Debian. I also notice that a Generic Java package (WAR) distribution is available. Am I correct in assuming that if we use a non-Ubuntu / non-Debian operating system, we can still install Jenkins via the WAR distribution without issue? Are we relegated to using Debian / Ubuntu if we’re going to install Jenkins on a Linux machine (with the possibility of Red Hat / Fedora / CentOS ruled out)? Thanks for any guidance from anybody who may have experience installing / maintaining a Jenkins instance on a Linux machine! - Jason -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/BY2PR12MB0599526179AD04C5679959E489AE0%40BY2PR12MB0599.namprd12.prod.outlook.com<https://groups.google.com/d/msgid/jenkinsci-users/BY2PR12MB0599526179AD04C5679959E489AE0%40BY2PR12MB0599.namprd12.prod.outlook.com?utm_medium=email&utm_source=footer>. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAArvnv22Md4_0YZdgOuAE%2BpZs9Vu3g0BdHJn5qm%2BnemwoAv5sg%40mail.gmail.com<https://groups.google.com/d/msgid/jenkinsci-users/CAArvnv22Md4_0YZdgOuAE%2BpZs9Vu3g0BdHJn5qm%2BnemwoAv5sg%40mail.gmail.com?utm_medium=email&utm_source=footer>. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/BY2PR12MB0599FD755ED454A44A65580589AE0%40BY2PR12MB0599.namprd12.prod.outlook.com<https://groups.google.com/d/msgid/jenkinsci-users/BY2PR12MB0599FD755ED454A44A65580589AE0%40BY2PR12MB0599.namprd12.prod.outlook.com?utm_medium=email&utm_source=footer>. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/e5eae65ec55445b4bc0b4b9f4ce53a7c%40partner.eso.org. For more options, visit https://groups.google.com/d/optout.
