|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-13764) CVS authenticati... [email protected] (JIRA)
- [JIRA] (JENKINS-13764) CVS authent... [email protected] (JIRA)
- [JIRA] (JENKINS-13764) CVS authent... [email protected] (JIRA)
- [JIRA] (JENKINS-13764) CVS authent... [email protected] (JIRA)
- [JIRA] (JENKINS-13764) CVS authent... [email protected] (JIRA)
- [JIRA] (JENKINS-13764) CVS authent... [email protected] (JIRA)
- [JIRA] (JENKINS-13764) CVS authent... [email protected] (JIRA)
- [JIRA] (JENKINS-13764) CVS authent... [email protected] (JIRA)

Do you have polling enabled, and does it work? The Environmental Variables we're passed during the checkout (and subsequent change-log) stage are for the node the work would be done on (the slave in your case) which is why they're resolving wrongly. If polling works then I should be able to make a change to generate change-logs on the slave and leave polling as it is, otherwise I'm going to have to consider our approach to rlog usage with SSH.