On Wed, Jun 13, 2012 at 10:35 AM, Roberto Nunnari <[email protected]> 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
[email protected]
