run jenkins slave on master about buildfarm_deployment HOT 4 CLOSED

I tried this and the jenkins puppet module is written such that the slave and master conflict. a2dc128

2014-12-09 08:26:13 +0000 Puppet (err): Duplicate declaration: Class[Java] is already declared in file /etc/puppet/modules/jenkins/manifests/init.pp:136; cannot redeclare at /etc/puppet/modules/jenkins/manifests/slave.pp:92 on node ip-172-31-6-118.us-west-1.compute.internal
2014-12-09 08:26:13 +0000 Puppet (err): Duplicate declaration: Class[Java] is already declared in file /etc/puppet/modules/jenkins/manifests/init.pp:136; cannot redeclare at /etc/puppet/modules/jenkins/manifests/slave.pp:92 on node ip-172-31-6-118.us-west-1.compute.internal

This is just a common issue which requires refactoring: https://ask.puppetlabs.com/question/10937/writing-modules-best-strategies-to-avoid-duplicate-declaration-for-files-packages-etc/ but it's of course inside the module we downloaded. For now can we not let some of these jobs run on the rest of the farm? maybe manually adding a tag to some of the slaves?

from buildfarm_deployment.

The goal is to run the jobs as close to the master as possible. Only running it on the machine will ensure to not make those jobs even slower. So running them on a random slave is not a good option.

from buildfarm_deployment.

Can you please fill a ticket upstream since it seems not to be listed in the jenkins puppet tracker?

from buildfarm_deployment.

Ticketed upstream: voxpupuli/puppet-jenkins#224

from buildfarm_deployment.