Hi team,
I am experiencing a nasty behavior when renaming a job.
The job itself is properly renamed, as well as the directory names on file system level.
However, the reference to the workspace is not updated. This has a side effect as we are using the git polling mechanism which is dependent on the .git folder within the workspace. As the job assumes no workspace is available it triggers a new build which is NOT what we want.
I know that there is the proposal to specify a custom workspace folder, see http://stackoverflow.com/questions/21682413/renaming-a-jenkins-job
But this is not what we want.
So I ask the team to modify the renaming function to also update the reference to the new workspace. is this possible?
Thanks a lot!
Stefan
- duplicates
-
JENKINS-25912 Workspace remains on disk after job has been ( deleted, moved, renamed )
-
- Open
-
[JENKINS-25967] Job rename does not update reference to new workspace
Link | New: This issue duplicates JENKINS-25912 [ JENKINS-25912 ] |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 159955 ] | New: JNJira + In-Review [ 196257 ] |