-
Bug
-
Resolution: Duplicate
-
Minor
-
None
-
Jenkins ver. 1.597 installed on Windows 8.1 (local test) and Windows Server 2008 R2 (production)
Use JobDSL plug in to create a job like this:
job('testjob') { customWorkspace('c:\\') }
Then delete customWorkspace and run JobDSL again:
job('testjob') {
}
The setting in the job is still activated and points to "c:\".
- depends on
-
JENKINS-21017 CLI update-job and POSTing config.xml cannot remove properties
-
- Resolved
-
- is duplicated by
-
JENKINS-39917 project update with dsl-script does not update "rootPom" settings for maven job
-
- Closed
-
- is related to
-
JENKINS-30548 Post build step not removed from generated Maven job
-
- Closed
-
[JENKINS-26825] JobDSL plugin doesn't reset customWorkspace setting
Link |
New:
This issue depends on |
Link |
New:
This issue is related to |
Workflow | Original: JNJira [ 160998 ] | New: JNJira + In-Review [ 180537 ] |
Link |
New:
This issue is duplicated by |
Description |
Original:
Use JobDSL plug in to create a job like this: {code} job { name( 'testjob') customWorkspace( 'c:\\' ) } {code} Then delete customWorkspace and run JobDSL again: {code} job { name( 'testjob') } {code} The setting in the job is still activated and points to "c:\". |
New:
Use JobDSL plug in to create a job like this: {code} job('testjob') { customWorkspace('c:\\') } {code} Then delete customWorkspace and run JobDSL again: {code} job('testjob') { } {code} The setting in the job is still activated and points to "c:\". |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |