|
||||||||
|
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/d/optout.
I tried this out using Windows slaves, but have had no success at reproducing the issue. I have added more logging for remote slaves (change 9987 on the main branch).
I have a theory that would be great if you could test out for me...
My gut feeling here is that this is a serialization issue and old objects are not being read/passed correctly.
To prove/disprove this the perfect way would be to setup a clean Jenkins install and see if you still have the bug. However, a quicker alternative would be to create a new Perforce Credentials object (delete the old one if you like) and perhaps try it with a new Jenkins Job.