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

Copy Artifacts of specific build number fails if build is triggered by upstream project.

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: copyartifact-plugin
    • Labels:
      None
    • Environment:
      Jenkins 1.493 running on Windows Server 2008 with Copy Artifacts 1.25
    • Similar Issues:

      Description

      We have the following setup: Three projects A, B and C, where a successful build of A triggers a build of B, which in turn triggers C (i.e. C depends on B, and B depends on A). Both A and B archive some artifacts, and the first step of B's build is to fetch the artifacts of A, and the first step of C's build is to fetch artifacts for both A and B.

      Now we want a specific build artifact of A (not the latest one) in project C and use the "specific build" option and giving a build number for which artifacts exist. Now, the build of C fails with "Unable to find a build for artifact copy from: A" if the build is triggered by the upstream project B. Building C manually seems to work initially, but once the build failed for the reason mentioned, only a Jenkins restart fixes the issue.

      As a workaround, it seems that using "latest saved build" works.

        Attachments

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              stefanheule Stefan Heule
            • Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: