There is a potential huge risk of skipping events for non pull request events. As of current implementation, the filtering is made via the isExcuded overriden method. As a collateral hiccup, the job is marked as disabled (and would be eventually be wiped with a configured Orphaned Item Strategy)

As per stephenconnolly comment at a GitHub PR;

The commit message "filter" should actually be using https://issues.jenkins-ci.org/browse/JENKINS-45502 longer term

That ticket would (hopefully) erase the drawbacks of the current implementation.

In the mean time, if you are fully aware of the current risk (or not using any Orphaned Item Strategy), I could work on it. What are your thoughts kburnett?

Again: Implementing this feature could cause a job to become erased, losing all of its run history

I upvoted JENKINS-45502. i don't fully understand the issue. i defer to your best judgement, unless stephenconnolly wants to weigh in.

Let me futher explain that risk, supposiong:

• You have a GitHub Organization or Bitbucket Team/Project job
• You have a X branch, with a Jenkinsfile
• You have an Orphaned Item Strategy, discarding disabled jobs
• You have a Scan Organization Triggers, set with an interval Y
• This feature is implemented to "skip" executions from branches
• You push one commit with [skip ci] in it message to that X branch

Whenever the event gets processed, the master branch would be tagged as excluded. Y time after, the Scan Organization Triggers will kick a full repo scan and the Orphaned Item Strategy will delete the Jenkinns job associated to that master branch, so you will end losing the whole master job history.

This seems like an edge case. Nobody should be relying on Jenkins to keep their entire build history, it's not an archival platform. And if they are by some chance, they shouldn't be using that Orphaned Item Strategy.

Please implement this feature.

Will try my best to add the feature this week, but (un)fortunately i have become pretty occupied, so there wont be any guarantees

Any update on this issue? We are very interested in using "[ci skip]" to skip maven release commits for example.

you are a hero.

kburnett, marbon and dbsanfte, could you test the opened pull request artifacts? Both hpi files found at https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fscm-trait-commit-skip-plugin/detail/feature%2FskippingBranches/1/artifacts (github and bitbucket) implement filtering branches on both [skip-ci] and [ci-skip] committed messages

Forgot to say that for testing this on bitbucket, another incrementals dependency must be manually installed (hpi from https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fbitbucket-branch-source-plugin/detail/PR-145/7/artifacts)

Needless to say that these are developments versions ans should be installed (desireably) on a test Jenkins instance

i got the dependent plugin from https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/cloudbees-bitbucket-branch-source/2.2.13-rc440.a1f1e6c1d925/, tested it out with jasquat, and it works as designed. in our context, the fact that the branch is tagged excluded and therefore deleted by the orphaned item strategy (exactly as witokondoria said it would be) actually is a dealbreaker. we are very excited about this feature, but i think we need to wait for JENKINS-45502 to be implemented so that "ci skip" can be implemented without this side effect (FYI, stephenconnolly / jamesdumay).

two additional notes:

• you need to specify "ci skip" without the hyphen
• when you specify behaviours, there are now two called "Commit message filtering behaviour" (one for pull requests and one for branches). they should probably have different names. see screenshot below.

thanks a ton, witokondoria.

Certainly, the expected tokens doesnt contain hypens (á la circleci - https://circleci.com/docs/2.0/skip-build/)
There is another PR, still unreviewed, to allow a regexp (instead of such fixed tokens).
Will fix the behaviour names so they differ
The outcome of JENKINS-45502 will indeed alter how the skipping is performed. Nevertheless, giving the ticket priority and activity, I wouldnt foresee it to receive work mid-term.

witokondoria any updates on this. We are really looking forward to this feature...

This should be included on the 0.2.0 released plugin. Should appear at the update center shortly.

Could you provide feedback, in order to close this ticket?

Thanks a lot witokondoria. Works as expected!

witokondoria sorry to bother, but was this developed just for Bitbucket or also for GitHub?

I am using version 0.4.0 of "GitHub Commit Skip SCM Behaviour" plugin on a Jenkins connected to GitHub Enterprise and my configuration looks as follows:

• GitHub Organisation project
• Build strategies (in this order; not sure if the order is important here):
  • Change requests
  • Regular branches
  • Skip build trigger if commit message contains
    • Pattern : skip

The documentation still states, that "The filtering is only performed for change request events, so push events to non-pull requests will be always run". But the same sentence is still in the doc for BitBucket and as far as I understand the discussion, this is working?

Any help would be appreciated.

Best regards, Tom