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

Merge commits are skipped if any of the merged commits contain the skip pattern

      We currently use a declarative pipeline with scm-skip like this:

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

      The Problem is that merge commits are often skipped, because one of the merged commits contains the skip pattern.

      Merge commits should only be skipped if the message of the merge commit directly contains the skip pattern.

       

          [JENKINS-63918] Merge commits are skipped if any of the merged commits contain the skip pattern

          Clemens Richter created issue -
          Clemens Richter made changes -
          Description Original: We currently use a declarative pipeline with scm-skip like this:

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

           

          The Problem is that merge commits are often skipped, because one of the merged commits contains the skip pattern.

           
          New: We currently use a declarative pipeline with scm-skip like this:

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

           

          The Problem is that merge commits are often skipped, because one of the merged commits contains the skip pattern.

           
          Clemens Richter made changes -
          Description Original: We currently use a declarative pipeline with scm-skip like this:

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

           

          The Problem is that merge commits are often skipped, because one of the merged commits contains the skip pattern.

           
          New: We currently use a declarative pipeline with scm-skip like this:

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

          The Problem is that merge commits are often skipped, because one of the merged commits contains the skip pattern.

           
          Clemens Richter made changes -
          Description Original: We currently use a declarative pipeline with scm-skip like this:

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

          The Problem is that merge commits are often skipped, because one of the merged commits contains the skip pattern.

           
          New: We currently use a declarative pipeline with scm-skip like this:

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

          The Problem is that merge commits are often skipped, because one of the merged commits contains the skip pattern.

          Merge commits should only be skipped if the message of the merge commit directly contains the skip pattern.

           
          Clemens Richter made changes -
          Summary Original: Merge commits are skipped if any of the merged commits contains skip pattern New: Merge commits are skipped if any of the merged commits contain the skip pattern
          Gabriella made changes -
          Link New: This issue is related to JENKINS-67436 [ JENKINS-67436 ]
          Alexander Brandes made changes -
          Remote Link New: This issue links to "https://github.com/jenkinsci/scmskip-plugin/pull/7 (Web Link)" [ 29016 ]
          Alexander Brandes made changes -
          Assignee Original: Gregor PlavĨak [ plavc ]
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]
          Zbynek Konecny made changes -
          Link New: This issue is duplicated by JENKINS-66843 [ JENKINS-66843 ]

            Unassigned Unassigned
            csrichter Clemens Richter
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: