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

Artifacts not found on re-runs of manual jobs in pipeline

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • build-pipeline-plugin
    • None
    • Jenkins 1.580 on RHEL and Java 1.7.0_65-b33. Using both Firefox and Chrome.

      Project A calls project B automatically with "Build other projects".

      Project B calls project C manually with "Build other projects (manual step)".

      All artifacts are archived and fingerprinted.

      Project B is set to copy artifacts from project A with "Upstream build that triggered this job".

      Project C is set to copy artifacts from project B with "Upstream build that triggered this job".

      Using the Build Pipeline plugin I can rerun A and/or B as much as I want in various pipeline builds of the same project. Each one moves the correct artifact versions around.

      I can run C manually once correctly. If I rerun it, it fails with this message:

      Unable to find a build for artifact copy from: B

      Repeat tries get repeat failures. If I jump to other pipeline builds of the same project and rerun C there, same thing, more failures.

      If I restart Jenkins, however, and try again, it will fail once more and then clear C from the pipeline. Then I can run it again without failure. But only once before it starts failing again.

      My test actually has five projects in a pipeline with the last two manually triggered. Both of these last two fail with the same behavior (even if I don't test all the way to the last project).

          [JENKINS-24883] Artifacts not found on re-runs of manual jobs in pipeline

          ikedam added a comment -

          That's an issue of build-pipeline plugin.
          Changed the component.

          It sounds that build-pipeline doesn't set "upstream cause" of the rerun of Project C.
          Attaching build.xml of the first run and the rerun of project C may help. They are located at ${JENKINS_HOME}/jobs/(name of Project C)/(build id)/build.xml.

          Rebuild Plugin may help you.

          ikedam added a comment - That's an issue of build-pipeline plugin. Changed the component. It sounds that build-pipeline doesn't set "upstream cause" of the rerun of Project C. Attaching build.xml of the first run and the rerun of project C may help. They are located at ${JENKINS_HOME}/jobs/(name of Project C)/(build id)/build.xml. Rebuild Plugin may help you.

          Dan Alvizu added a comment -

          Linking JENKINS-30801 - they address a common problem of how Actions copied from previous builds

          Dan Alvizu added a comment - Linking JENKINS-30801 - they address a common problem of how Actions copied from previous builds

          Dan Alvizu added a comment -

          There is a PR for this fix:

          https://github.com/jenkinsci/build-pipeline-plugin/pull/85/files

          I have incorporated this into my own here and added a test:

          https://github.com/jenkinsci/build-pipeline-plugin/pull/89

          Dan Alvizu added a comment - There is a PR for this fix: https://github.com/jenkinsci/build-pipeline-plugin/pull/85/files I have incorporated this into my own here and added a test: https://github.com/jenkinsci/build-pipeline-plugin/pull/89

          Dan Alvizu added a comment -

          Merged to master will be in 1.4.9 release

          Dan Alvizu added a comment - Merged to master will be in 1.4.9 release

            dalvizu Dan Alvizu
            juanitogan Matt Jernigan
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: