Thanks...I'm not worried about the master and I know I don't need Tomcat,
but that is how we have been deploying the master.

I'm now trying to configure/add slaves and the settings for the Master
don't directly translate to the slaves, at least in ways that are obvious.
 For example, I told the master to automatically install multiple JDK
versions.  Do the slaves automatically install JDK's as well?  Seems broken
if not, but I don't know how to tell if it works as I've not reached that
point yet on the slaves.

The GIT install on the slaves so far has been a manual process.  I need to
get the GIT binaries and then the SSH keys installed in the right place
(with the right permissions) and then I think I need to add the GIT server
key to the authorized_keys file.  I might be able to share/copy them but
I've not worked that out yet.

Once I work out GIT, I need to do work out Maven, SVN, JDK's, ANT, SONAR,
etc. settings.

The frustration being that I haven't seen an obvious way to translate the
server settings (tools, config, etc.) easily to the slaves so that the jobs
just work and I haven't found anything explaining how to do it or a best
practice for doing it once and easily duplicating those steps to additional
slaves.



On Wed, Dec 12, 2012 at 12:59 AM, frank stockmans <[email protected]
> wrote:

> I tend to run all my builds on slaves.
> - make sure the workspace on slaves is different from that on the master
> - have a recent version of java on the slave
> - be able to ssh to it and our .cshrc should throw any error's or messages
> to the terminal when you get there
> Slaves need to be able to get to your git/SVN servers.
>
> You don't need tomcat to run a jenkins master. You can run it natively.
> >java --jar jenkins.war &
> Backup $JENKINS_HOME on the master. It is all you need.
>
> Have Fun
> Frank
>
>
> On Tuesday, December 11, 2012 3:33:09 PM UTC-8, Jeff Vincent wrote:
>
>> I'm starting to setup a new master/slave configuration using Ubuntu 12.10
>> + Tomcat 7.  I couldn't find any real docs regarding slaves and could use
>> some clarification on best practices particularly with tools.
>>
>> My builds use:
>>
>> Git or SVN
>> Maven
>> SVN
>> Java 6 and 7
>>
>> Additionally I have configured ANT for some legacy projects (that I may
>> not convert) and with maven I use SONAR and the maven release plugin.
>>
>> What is the best practice for getting a slave configured?
>>
>> So far, the issues I've had relate to configuring GIT, git ssh-key auth,
>> and Maven settings.  I'm sure the list will continue.
>>
>> Any help is appreciated to make this less painful...
>>
>> --
>> Jeff Vincent
>> [email protected]
>>
>> See my LinkedIn profile at:
>> http://www.linkedin.com/in/**rjeffreyvincent<http://www.linkedin.com/in/rjeffreyvincent>
>> I ♥ DropBox <http://db.tt/9O6LfBX> !!
>>
>>


-- 
Jeff Vincent
[email protected]
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent
I ♥ DropBox <http://db.tt/9O6LfBX> !!

Reply via email to