You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 22, 2022. It is now read-only.
Currently there is only one option to skip triggering builds by pattern in commit message. 'ci-skip' plugin (https://github.com/banyan/jenkins-ci-skip-plugin), which could skip builds with 'NON_BUILT' resolution if they contain '[ci skip]' in every commit message related to current build. But the best place to do this is the code of Jenkins GIT plugin as you can just not trigger a build for this case while ci-ckip plugin triggers build (!) and finishes it quickly as 'NON_BUILT' (and so, Jenkins Git plugin could just skip build instead of making redundant gray builds appear in list)
Example of new option usage: skip triggering a build if all it's commits contain '[maven-release-plugin]' as prefix (which is default for maven-release-plugin)
The text was updated successfully, but these errors were encountered:
Currently there is only one option to skip triggering builds by pattern in commit message. 'ci-skip' plugin (https://github.com/banyan/jenkins-ci-skip-plugin), which could skip builds with 'NON_BUILT' resolution if they contain '[ci skip]' in every commit message related to current build. But the best place to do this is the code of Jenkins GIT plugin as you can just not trigger a build for this case while ci-ckip plugin triggers build (!) and finishes it quickly as 'NON_BUILT' (and so, Jenkins Git plugin could just skip build instead of making redundant gray builds appear in list)
SVN plugin already supports this: http://stackoverflow.com/questions/8037230/run-jenkins-job-if-only-scm-comment-match-pattern
Example of new option usage: skip triggering a build if all it's commits contain '[maven-release-plugin]' as prefix (which is default for maven-release-plugin)
The text was updated successfully, but these errors were encountered: