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

If a pipeline skip is setup to delete skiped builds all future builds are skipped

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • scmskip-plugin
    • None

      It seems like a commit with [skip ci] in its commit message is never "consumed" if the build is also deleted and continues to enforce skipping forever. With more and more commits becoming part of the "most recent build"

       

      Steps to reproduce:

      Create a pipeline jenkins file containing:

       

       

      pipeline {
      
          agent any
          stages {
              stage('CheckSkip') {
                  steps {
                      scmSkip(deleteBuild: true, skipPattern:'.*\\[skip ci\\].*')
                  }
              }
      ....

       

       

      Make a commit that has [skip ci] in its commit message. Push

      Make a second commit that does not have [skip ci] in its commit message. Push

       

      Expected result:

      The second commit and push kicks off a build that is not skipped

      Actual result:

      The second commit and push does not kick off a build (and Jenkins believes that the job contains all commits since the first skip. This continues for the 3rd, 4th etc push until deleteBuild is turned off, then it calms down and builds are allowed again.

       

       

          [JENKINS-66843] If a pipeline skip is setup to delete skiped builds all future builds are skipped

          Richard Tingle created issue -
          Richard Tingle made changes -
          Description Original: It seems like a commit with [skip ci] in its commit message is never "consumed" is the build is also deleted and continues to enforce skipping forever. With more and more commits becoming part of the "most recent build"

          !image-2021-10-10-13-58-47-679.png|width=735,height=389!

           

          *Steps to reproduce:*

          Create a pipeline jenkins file containing:

           

           
          {code:java}
          pipeline {

              agent any
              stages {
                  stage('CheckSkip') {
                      steps {
                          scmSkip(deleteBuild: false, skipPattern:'.*\\[skip ci\\].*')
                      }
                  }
          ....{code}
           

           

          Make a commit that has [skip ci] in its commit message. Push

          Make a second commit that does not have [skip ci] in its commit message. Push

           

          *Expected result:*

          The second commit and push kicks off a build that is not skipped

          *Actual result:*

          The second commit and push does not kick off a build (and Jenkins believes that the job contains all commits since the first skip. This continues for the 3rd, 4th etc push until deleteBuild is turned off, then it calms down and builds are allowed again.

           

           
          New: It seems like a commit with [skip ci] in its commit message is never "consumed" if the build is also deleted and continues to enforce skipping forever. With more and more commits becoming part of the "most recent build"

          !image-2021-10-10-13-58-47-679.png|width=735,height=389!

           

          *Steps to reproduce:*

          Create a pipeline jenkins file containing:

           

           
          {code:java}
          pipeline {

              agent any
              stages {
                  stage('CheckSkip') {
                      steps {
                          scmSkip(deleteBuild: false, skipPattern:'.*\\[skip ci\\].*')
                      }
                  }
          ....{code}
           

           

          Make a commit that has [skip ci] in its commit message. Push

          Make a second commit that does not have [skip ci] in its commit message. Push

           

          *Expected result:*

          The second commit and push kicks off a build that is not skipped

          *Actual result:*

          The second commit and push does not kick off a build (and Jenkins believes that the job contains all commits since the first skip. This continues for the 3rd, 4th etc push until deleteBuild is turned off, then it calms down and builds are allowed again.

           

           
          Richard Tingle made changes -
          Description Original: It seems like a commit with [skip ci] in its commit message is never "consumed" if the build is also deleted and continues to enforce skipping forever. With more and more commits becoming part of the "most recent build"

          !image-2021-10-10-13-58-47-679.png|width=735,height=389!

           

          *Steps to reproduce:*

          Create a pipeline jenkins file containing:

           

           
          {code:java}
          pipeline {

              agent any
              stages {
                  stage('CheckSkip') {
                      steps {
                          scmSkip(deleteBuild: false, skipPattern:'.*\\[skip ci\\].*')
                      }
                  }
          ....{code}
           

           

          Make a commit that has [skip ci] in its commit message. Push

          Make a second commit that does not have [skip ci] in its commit message. Push

           

          *Expected result:*

          The second commit and push kicks off a build that is not skipped

          *Actual result:*

          The second commit and push does not kick off a build (and Jenkins believes that the job contains all commits since the first skip. This continues for the 3rd, 4th etc push until deleteBuild is turned off, then it calms down and builds are allowed again.

           

           
          New: It seems like a commit with [skip ci] in its commit message is never "consumed" if the build is also deleted and continues to enforce skipping forever. With more and more commits becoming part of the "most recent build"

          !image-2021-10-10-13-58-47-679.png|width=735,height=389!

           

          *Steps to reproduce:*

          Create a pipeline jenkins file containing:

           

           
          {code:java}
          pipeline {

              agent any
              stages {
                  stage('CheckSkip') {
                      steps {
                          scmSkip(deleteBuild: true, skipPattern:'.*\\[skip ci\\].*')
                      }
                  }
          ....{code}
           

           

          Make a commit that has [skip ci] in its commit message. Push

          Make a second commit that does not have [skip ci] in its commit message. Push

           

          *Expected result:*

          The second commit and push kicks off a build that is not skipped

          *Actual result:*

          The second commit and push does not kick off a build (and Jenkins believes that the job contains all commits since the first skip. This continues for the 3rd, 4th etc push until deleteBuild is turned off, then it calms down and builds are allowed again.

           

           
          Gabriella made changes -
          Link New: This issue is related to JENKINS-67436 [ JENKINS-67436 ]
          Zbynek Konecny made changes -
          Link New: This issue duplicates JENKINS-63918 [ JENKINS-63918 ]
          Zbynek Konecny made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

            plavc Gregor PlavĨak
            richardtingle Richard Tingle
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: