Re: where to do the build
On Wed, Jun 13, 2012 at 10:35 AM, Roberto Nunnari wrote: > > humm.. really there isn't a paramenter to pass to jenkins that tells it > where to do the build? There is a JENKINS_HOME setting, but on the master that affects the job and artifact storage as well as the build execution. And on distribution-packaged versions, the default is already going to be set for the place that distribution thinks is appropriate for servers to be writing data. The path of least resistance is usually to put the resources where the distribution wants them instead of having to re-adjust your configuration settings after every update. (So, maybe mount a big partition as /var/lib/jenkins, or at least put /var on its own drive). > oh well.. then probably, as you advice, the best option is to run the build > on another executor, may it be on the same server, elsewhere or on the HPC > cluster.. Using build slaves makes things very flexible - and easy to do cross-platform work as well. It is mostly transparent from the user side. -- Les Mikesell lesmikes...@gmail.com
Re: where to do the build
2012/6/13 Les Mikesell > On Wed, Jun 13, 2012 at 9:44 AM, Roberto Nunnari > wrote: > > Hi everybody. > > > > One more question.. > > I just noticed in the page 'jenkins >> nodes' that 'Free disk space' is > > talking about the system filesystem.. > > I want jenkins to do it work (checkout, build, etc..) on a different > > filesystem and folder, say /opt/jenkins.. how do I change that? > > > > Having jenkins being installed from an ubuntu distro, it went spreaded > all > > over the place.. at least /var/lib/jenkins /usr/share/jenkins and > > /var/run/jenkins/ > > > > jenkins is started with the following args: > > JENKINS_ARGS="--webroot=$JENKINS_RUN/war --httpPort=$HTTP_PORT > > --ajp13Port=$AJP_PORT --preferredClassLoader=java.net.URLClassLoader > > --prefix=/jenkins" > > > > Any hints please? > > One approach - that is probably easier than messing with the > configuration of a packaged (.deb/.rpm) version is to simply start a > build slave that happens to be on the same server. Basically all you > have to do for this is set up ssh keys so the jenkins user on the > master can do passwordless commands as the target user on the target > system (you can use ssh-copy-id for this), and set up the node to be > started by ssh. Everything else pretty much takes care of itself and > the builds happen in the home directory of the target user. It won't > matter if that is on the same host or elsewhere. > > -- > Les Mikesell > lesmikes...@gmail.com > humm.. really there isn't a paramenter to pass to jenkins that tells it where to do the build? oh well.. then probably, as you advice, the best option is to run the build on another executor, may it be on the same server, elsewhere or on the HPC cluster.. Thank you very much for your help. Best regards.
Re: where to do the build
On Wed, Jun 13, 2012 at 9:44 AM, Roberto Nunnari wrote: > Hi everybody. > > One more question.. > I just noticed in the page 'jenkins >> nodes' that 'Free disk space' is > talking about the system filesystem.. > I want jenkins to do it work (checkout, build, etc..) on a different > filesystem and folder, say /opt/jenkins.. how do I change that? > > Having jenkins being installed from an ubuntu distro, it went spreaded all > over the place.. at least /var/lib/jenkins /usr/share/jenkins and > /var/run/jenkins/ > > jenkins is started with the following args: > JENKINS_ARGS="--webroot=$JENKINS_RUN/war --httpPort=$HTTP_PORT > --ajp13Port=$AJP_PORT --preferredClassLoader=java.net.URLClassLoader > --prefix=/jenkins" > > Any hints please? One approach - that is probably easier than messing with the configuration of a packaged (.deb/.rpm) version is to simply start a build slave that happens to be on the same server. Basically all you have to do for this is set up ssh keys so the jenkins user on the master can do passwordless commands as the target user on the target system (you can use ssh-copy-id for this), and set up the node to be started by ssh. Everything else pretty much takes care of itself and the builds happen in the home directory of the target user. It won't matter if that is on the same host or elsewhere. -- Les Mikesell lesmikes...@gmail.com
Re: where to do the build
Hi Roberto, perhaps this thread might be helpful for you: http://jenkins.361315.n4.nabble.com/Is-it-possible-to-store-artifacts-on-a-different-drive-from-the-quot-jobs-quot-folder-td4190962.html Cheers, Simon. -- Roberto Nunnari (13.06.2012 16:44): Hi everybody. One more question.. I just noticed in the page 'jenkins >> nodes' that 'Free disk space' is talking about the system filesystem.. I want jenkins to do it work (checkout, build, etc..) on a different filesystem and folder, say /opt/jenkins.. how do I change that? Having jenkins being installed from an ubuntu distro, it went spreaded all over the place.. at least /var/lib/jenkins /usr/share/jenkins and /var/run/jenkins/ jenkins is started with the following args: JENKINS_ARGS="--webroot=$JENKINS_RUN/war --httpPort=$HTTP_PORT --ajp13Port=$AJP_PORT --preferredClassLoader=java.net.URLClassLoader --prefix=/jenkins" Any hints please? Thank you!
