Missing release configuration option on jenkins-slave charm

[Charles Butler]

When adding a jenkins-slave to a Jenkins deployed node where the release flag is set to trunk, deploying jenkins-slave does not register with the jenkins master node with a 403 forbidden error

Failing to obtain http://10.0.3.182:8080/computer/jenkins-slave-0/slave-agent.jnlp
java.io.IOException: Failed to load http://10.0.3.182:8080/computer/jenkins-slave-0/slave-agent.jnlp: 403 Forbidden
 at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:270)
 at hudson.remoting.Launcher.run(Launcher.java:218)
 at hudson.remoting.Launcher.main(Launcher.java:192)
Waiting 10 seconds before retry

[Diogo Matsubara (matsubara)]

I ran into this bug and I don't think it's related to the release option (or lack of in the jenkins-slave charm). I think it's due to https://issues.jenkins-ci.org/browse/JENKINS-16273 and the proposed fix in the bug report is to include -jnlpCredentials parameter to the way jenkis slave is started. It looks like this used to work on previous versions because anoymous users could download the slave.jnlp without authentication and current versions won't allow that.

I have a jenkins-slave charm branch here: lp:~matsubara/charms/trusty/jenkins-slave/trusty-jenkins-slave which updates the hook to request the credentials as well as a jenkins master charm branch here: lp:~matsubara/charms/trusty/jenkins/jenkins-bundle which adds support to sending credentials to the slave.