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

changeset does not work when retrying a pipeline

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • pipeline
    • None
    • EC2 running AWS-Linux 2
      Jenkins 2.262

      I have a Jenkinsfile with a stage that only runs when on master branch and any of a group of changesets occur as such:

      allOf {
      branch 'master'
      anyOf

      { BUNCH OF DIFFERENT CHANGESETS GO HERE }

      }

       

      this caused a build to trigger appropriately but the build failed because something was offline (docker daemon wasn't running). I tried to hit retry on the entire pipeline and it started and "skipped due to when conditional" Logically, it should have the same results as the original pipeline did for these cases as it should be running on the same commit. It even detects in the list of changes the commit that triggered it.

            Unassigned Unassigned
            khumps Kevin Humphreys
            Votes:
            4 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: