|
||||||||
|
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.
Seeing this on the latest (v1.515). Jenkins doesn't even delete the workspace on slaves when the job is deleted.
It's very easy to reproduce:
1) Create a job named "A" with empty configuration
2) Run the job "A"
3) On slave, find the directory "A" under jenkins/workspace
4) Rename the job "A" to "B"
5) On slave, see that directory "A" is still there and that there is no directory "B"
6) Re-run the job (named as "B" now)
7) On slave, see that a new directory with name of "B" has been created. The old directory "A" is still there as well
8) Delete job "B"
9) On slave, see that both directories "A" and "B" are still there...
This is a real issue when jobs are dynamically created and deleted based on branches (http://entagen.github.io/jenkins-build-per-branch/).