• Type: Improvement
• Resolution: Won't Fix
• Priority: Blocker
• Component/s: core, other
• Labels:

  None
• Environment:

  Platform: All, OS: All

[JENKINS-2644] Allow artifact archiver to search outside of workspace for artifacts

Collapse comment: Garen Parham added a comment - 2012-01-04 04:59, Edited by Garen Parham - 2012-01-05 22:30

Garen Parham added a comment - 2012-01-04 04:59 - edited

Without this feature, I'm stuck between a rock and a hard place in Jenkins: using a dynamic view via ClearCase, it appears to be impossible to both (1) ensure the view is started (and any desired vobs mounted) before the job executes and (2) archive any artifacts.

(1) Has other issues already filed for it, but to solve it currently I have to use an upstream job that gets started by the parameterized-trigger plugin. This also means that the "real" job of interest executes until it gets to the "trigger/call builds on other projects", and executes the upstream job, at which point it has already tried to access the custom workspace.

For (2) it of course does work if I use a custom workspace if the desired view already exists and has a valid path before the job starts, but if it doesn't then fails.

Expand comment: Garen Parham added a comment - 2012-01-04 04:59, Edited by Garen Parham - 2012-01-05 22:30

Garen Parham added a comment - 2012-01-04 04:59 - edited Without this feature, I'm stuck between a rock and a hard place in Jenkins: using a dynamic view via ClearCase, it appears to be impossible to both (1) ensure the view is started (and any desired vobs mounted) before the job executes and (2) archive any artifacts. (1) Has other issues already filed for it, but to solve it currently I have to use an upstream job that gets started by the parameterized-trigger plugin. This also means that the "real" job of interest executes until it gets to the "trigger/call builds on other projects", and executes the upstream job, at which point it has already tried to access the custom workspace. For (2) it of course does work if I use a custom workspace if the desired view already exists and has a valid path before the job starts, but if it doesn't then fails.

Collapse comment: Jesse Glick added a comment - 2013-08-21 13:37

Jesse Glick added a comment - 2013-08-21 13:37

Either add a shell build step to copy desired files into the workspace, or write a simple plugin to archive artifacts from other locations (integrating with JENKINS-17236 when available).

Expand comment: Jesse Glick added a comment - 2013-08-21 13:37

Jesse Glick added a comment - 2013-08-21 13:37 Either add a shell build step to copy desired files into the workspace, or write a simple plugin to archive artifacts from other locations (integrating with JENKINS-17236 when available).