|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
Confirmed this is still a bug with git-client-plugin 1.6.4 and git-plugin 2.0.4. I suspect the issue lies more with the multi-configuration project placing the label/slave-name in the top level directory, but am not sure another solution is feasible.
Refer to the attached picture trying to illustrate the problem. One of the slaves is selected to host the "root workspace", and if that slave also is used as part of that multi-configuration job, then there will be a label/slave-name directory within the root workspace on the slave. When the clean is performed in the root workspace, it will remove the label/slave-name directory completely.