Hi Michael, (I was OOO for the past week) Regarding the systemd script, I see that it doesn't make use of the EnvironmentFile property. I've managed to successfully start the slave process only by *hard-coding* parameters into to the java command. whenever I tried using env vars from the ' */etc/sysconfig/jenkins-slave*' the process failed to start.
Any idea on that? Thanks, Yarden On Tuesday, December 29, 2015 at 1:34:36 AM UTC+2, Michael Neale wrote: > > Hi Yarden. > > I had a systemd script I used for "OPE" style slaves (which are basically > jnlp slaves): https://gist.github.com/michaelneale/9635744 > > (a bit more written about it here), it worked for me as I learned systemd, > may be able to adapt it: > http://documentation.cloudbees.com/docs/dev-at-cloud/On-Premise+Executors.html?query=systemd#running-the-slave-with-systemd-on-linux > > On Saturday, December 26, 2015 at 6:26:04 PM UTC+11, Yarden Bar wrote: >> >> Hi all, >> I'm using this >> <https://github.com/seekingalpha/puppet-jenkins/tree/enable_systemd_support> >> forked >> Puppet module to configure a Jenkins slave instance. >> >> The systemd Unit script >> <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fseekingalpha%2Fpuppet-jenkins%2Fblob%2Fenable_systemd_support%2Ftemplates%2Fjenkins-slave.systemd.erb&sa=D&sntz=1&usg=AFQjCNEDXFWTCGk5uAQFng5VIR1UaH-Z2g> >> doesn't >> start the process. If I su to root, source the /etc/sysconfig/jenkins-slave >> file and run the start-stop-daemon command as-is, the slave starts and >> connects to the master. >> >> Any idea? >> >> Thanks in advance, >> Yarden >> > -- 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/5fa0e5e2-43b8-4195-8830-57efeb2c2e6c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
