-
New Feature
-
Resolution: Done
-
Major
-
None
-
-
[GSoC] Sprint 1, [GSoC] Sprint 2
When allocating the workspace using exwsAllocate step, provide a unique workspace for each Pull Request. So the allocated workspace path on the disk shall be like: $physicalPathOnDisk/$jobName/$pullRequestNumber/$buildNumber
Additional details.
- The relative path is configurable within Build DSL
- [Nice2have]: Be able to specify path in the template. Maybe complicated, because for template we may need to resolve build environment variables
- Workspace cleanup should work properly with such workspaces
- Plugin should prevent workspace collisions (for example $physicalPathOnDisk/$jobName/A and $physicalPathOnDisk/$jobName/A/B)
- is duplicated by
-
-
- Resolved
-
[JENKINS-35975] Configurable relativePath within the Disk Pool for a job
| Epic Link |
New:
|
| Description |
Original:
When allocating the workspace using {{exwsAllocate}} step, provide a unique workspace for each Pull Request. So the allocated workspace path on the disk shall be like: {{$physicalPathOnDisk/$jobName/$buildNumber/$pullRequestNumber}} Additional details TBD. Reference: https://github.com/martinda/external-workspace-manager/blob/master/README.md#advanced-usage-git-pull-request |
New:
When allocating the workspace using {{exwsAllocate}} step, provide a unique workspace for each Pull Request. So the allocated workspace path on the disk shall be like: {{$physicalPathOnDisk/$pullRequestNumber/$jobName/$buildNumber}} Additional details TBD. Reference: https://github.com/martinda/external-workspace-manager/blob/master/README.md#advanced-usage-git-pull-request |
| Description |
Original:
When allocating the workspace using {{exwsAllocate}} step, provide a unique workspace for each Pull Request. So the allocated workspace path on the disk shall be like: {{$physicalPathOnDisk/$pullRequestNumber/$jobName/$buildNumber}} Additional details TBD. Reference: https://github.com/martinda/external-workspace-manager/blob/master/README.md#advanced-usage-git-pull-request |
New:
When allocating the workspace using {{exwsAllocate}} step, provide a unique workspace for each Pull Request. So the allocated workspace path on the disk shall be like: {{$physicalPathOnDisk/$jobName/$pullRequestNumber/$buildNumber}} Additional details TBD. Reference: https://github.com/martinda/external-workspace-manager/blob/master/README.md#advanced-usage-git-pull-request |
| Summary | Original: Git pull request for the external workspace manager | New: Configurable relativePath within the Disk Pool for a job |
| Description |
Original:
When allocating the workspace using {{exwsAllocate}} step, provide a unique workspace for each Pull Request. So the allocated workspace path on the disk shall be like: {{$physicalPathOnDisk/$jobName/$pullRequestNumber/$buildNumber}} Additional details TBD. Reference: https://github.com/martinda/external-workspace-manager/blob/master/README.md#advanced-usage-git-pull-request |
New:
When allocating the workspace using {{exwsAllocate}} step, provide a unique workspace for each Pull Request. So the allocated workspace path on the disk shall be like: {{$physicalPathOnDisk/$jobName/$pullRequestNumber/$buildNumber}} Additional details. * The relative path is configurable within Build DSL * [Nice2have]: Be able to specify path in the template. Maybe complicated, because for template we may need to resolve build environment variables * Workspace cleanup should work properly with such workspaces * Plugin should prevent workspace collisions (for example $physicalPathOnDisk/$jobName/A and $physicalPathOnDisk/$jobName/A/B) Reference: https://github.com/martinda/external-workspace-manager/blob/master/README.md#advanced-usage-git-pull-request |
| Rank | New: Ranked higher |
| Sprint | New: [GSoC] Sprint 1 [ 81 ] |
| Rank | New: Ranked lower |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |