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
Git plugin implements behaviours (traits) that prevent to run builds for commits that contain specific commit message ("Polling ignores commits with certain messages", MessageExclusion) or contain changes of specific files ("Polling ignores commits in certain paths", PathRestriction).
Is it possible to add similar behaviour to GitLab Branch Source plugin? If so, what is the easiest way to achieve this?
Upstream changes
No response
The text was updated successfully, but these errors were encountered:
Currently, it does not seem that these traits exist for gitlab-branch-source.
Triggering only when changes to specific files in the repo is possible using the "Build included regions" strategy from "Pipeline: Multibranch build strategy extension" plug-in. This has several drawbacks, though:
the strategies only apply when triggered by the webhook, not on a new scan (don't know if this a bug in gitlab-branch-source/Multibranch build strategy extension or if this is the expected behaviour)
the extension was a little bit unreliably in our setup, triggering the build even if the "region" was not changed
for some of the strategies an actual checkout is required. So they are not working for number 1 builds. I think this is not an issue with the "Build included regions", though. Only for other strategies like "Cancel ci by ignore file"
There is another gitlab plugin that, has this option (ciSkip) and a lot more options for the webhooks.
Unfortunately it's not supporting merge requests for multibranch pipelines.
This is the description of ciSkip:
If enabled, then the build will be skipped when a GitLab comment includes the text ci-skip.
Personally, I don't understand why it's not supporting merge requests for multibranch pipelines, because it looks like the hook only must be delegated to the source branch of the merge request.
It would be cool if only one plugin handled the webhooks, not two plugins with half of the functionality.
What feature do you want to see added?
Git plugin implements behaviours (traits) that prevent to run builds for commits that contain specific commit message ("Polling ignores commits with certain messages", MessageExclusion) or contain changes of specific files ("Polling ignores commits in certain paths", PathRestriction).
Is it possible to add similar behaviour to GitLab Branch Source plugin? If so, what is the easiest way to achieve this?
Upstream changes
No response
The text was updated successfully, but these errors were encountered: