Hi,

We have a problem when passing Build selector for Copy Artifact as a parameter filter for an older job/build.

Suppose 3 Jobs:

• Job 1: DepJob
• Job 2: SubJob
  • Build selector for Copy Artifact Parameter: SELECT_ME
    • Default selector : Specific build
    • Build number : 123
  • Build step: Copy artifacts from another project:
    • Project Name : DepJob
    • Which build : Specified by a build parameter
      • Parameter Name : SELECT_ME
• Job 3: MainJob
  • Build selector for Copy Artifact Parameter: SELECT_DEPJOB
    • Default selector : Specific build
    • Build number : 123
  • Build step: Copy artifacts from another project:
    • Project Name : SubJob
    • Which build : Latest successful build
    • Parameter filters : SELECT_ME=$SELECT_DEPJOB

Quick issue description

When last successful build of SubJob has been built with an older version of the Copy Artifact Plugin, then MainJob cannot find the artifacts although they exist!

Details

1. DepJob has a build 123.
2. SubJob performs some builds with Copy Artifact Plugin version 1.26:
   • Build selector for Copy Artifact Parameter:
     • SELECT_ME: Specific build -> 123
3. Update Copy Artifact Plugin
4. MainJob performs build with Copy Artifact Plugin version 1.31:
   • Build selector for Copy Artifact Parameter:
     • SELECT_DEPJOB: Specific build -> 123
5. MainJob build fails since it cannot find atifacts with SELECT_ME: Specific build -> 123 in the old builds of SubJob!

This is a blocker for us since we have a very large project which uses this kind of constructions for packaging all sub-projects (aka sub jobs).

We recently updated the Copy Artifact Plugin, but we still need lots of artifacts the old(er) sub-projects (for which currently no rebuilt is needed).