Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-10652

Copy artifacts using permalink of Latest Promotion does not get the proper artifacts

      To reproduce: Create a build (build A), which creates an artifact which is archived and fingerprinted. Configure this build to promote on both a successful completion of that downstream Build A, and a manual approval. Configure the promotion action step to run another build (Build B).

      In Build B, select Copy artifacts->using permalink -> Latest promotion<promotion name>.

      Run build A 4 times, getting build numbers 1, 2, 3, and 4. Promote build 3. Note that Build B copies over the artifact from the 3rd build of Build A. This is correct. Promote build 4. Note that Build B copies over the artifact from the 4th build of Build A. This is correct. Promote build 2. Note that build B copies over the artifact from the 4th build of Build A, instead of the 2nd build of build A. This is incorrect.

          [JENKINS-10652] Copy artifacts using permalink of Latest Promotion does not get the proper artifacts

          dsheth added a comment -

          I suppose this depends on the definition of "Latest Promotion". If "Latest Promotion" means the highest build number of any of the promoted builds, then the plugin is acting as designed. If "Latest Promotion" means the promotion which took place most recently (i.e. the promotion which kicked off the build of B) then it is not working correctly.

          If it is acting as designed, then I suppose this becomes an enhancement request to have a way to have the artifacts of any arbitrary build be the inputs to another build.

          dsheth added a comment - I suppose this depends on the definition of "Latest Promotion". If "Latest Promotion" means the highest build number of any of the promoted builds, then the plugin is acting as designed. If "Latest Promotion" means the promotion which took place most recently (i.e. the promotion which kicked off the build of B) then it is not working correctly. If it is acting as designed, then I suppose this becomes an enhancement request to have a way to have the artifacts of any arbitrary build be the inputs to another build.

            Unassigned Unassigned
            dsheth dsheth
            Votes:
            3 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: