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

Race condition when copying archived artifacts in another job

      In a Multijob setup, we create and archive some artifacts in a sub job, which we afterwards copy into the parent job to be consumed during a "docker build" step (which directly follows the "copy artifacts" step).

      Before switching to S3 artifact manager, everything went fine, but afterwards the jobs started to fail because the "docker build" step couldn't find the artifacts Jenkins said it had copied successfully.

      We could reproduce this in a test job. There is some delay between "artifacts copied" and "artifacts being accessible", and the artifact in our case was just 15kB.

      This renders the plugin unusable (for us), hence the "Blocker".

          [JENKINS-71768] Race condition when copying archived artifacts in another job

          Dirk Heinrichs added a comment - - edited
          1. This nice but I guess the delay would vary depending on artifact size, right?
          2. This shouldn't be needed at all, since that's what I would expect from the plugin in the first place. If it says they have been copied, they should have been copied.
          3. Multijobs don't have stash/unstash, that's a pipeline thing.

          Dirk Heinrichs added a comment - - edited This nice but I guess the delay would vary depending on artifact size, right? This shouldn't be needed at all, since that's what I would expect from the plugin in the first place. If it says they have been copied, they should have been copied. Multijobs don't have stash/unstash, that's a pipeline thing.

            Unassigned Unassigned
            dhs Dirk Heinrichs
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: