-
Bug
-
Resolution: Fixed
-
Minor
-
Jenkins 2.190.3
scmskip 1.0.3
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.
- is duplicated by
-
JENKINS-66843 If a pipeline skip is setup to delete skiped builds all future builds are skipped
-
- Resolved
-
- is related to
-
JENKINS-67436 SCM Skip Plugin does not abort pipeline
-
- Resolved
-
- links to
[JENKINS-63918] Merge commits are skipped if any of the merged commits contain the skip pattern
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. |
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. |
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. |
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 |
Link |
New:
This issue is related to |
Remote Link | New: This issue links to "https://github.com/jenkinsci/scmskip-plugin/pull/7 (Web Link)" [ 29016 ] |
Assignee | Original: Gregor Plavčak [ plavc ] | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Link |
New:
This issue is duplicated by |
I made a fix for this bug and provide a fixed plugin for download: https://github.com/jenkinsci/scmskip-plugin/pull/9