|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
As for your internal machine and 403, I assume you require a login for Jenkins. This means that the slave will not have access to the slave.jar. To get passed the 403 you can either, enable anonymous read access, which will allow anyone to access the slave.jar (should only be considered if running on a trusted closed network) or add authentication to your request using the -jnlpCredential parameter.
I have not tried it, but this post seems to show how to use the -jnlpCredential parameter. http://stackoverflow.com/questions/16880110/login-to-jenkins-via-url