The pipeline definition only changes in the branch(es) that you change it in. This is not universal across all branches, thus triggering a build in a branch in which the pipeline hasn't changed would not really have the effect that you are desiring. The only way to make this work is to make the changes in every branch, either by changing them directly or by a merge.
On Friday, May 17, 2019 at 11:41:42 AM UTC-5, Jan Hentschel wrote: > > Hi, > > I have some pipelines defined in a separate project, which are then used > via an include in the actual project. What I'm trying to achieve is to > retrigger builds for all branches in the actual project if their GitLab > pipeline definition has changed. Does anyone has an idea on how to do that? > > Best, Jan > -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/02b5fb16-95b5-4b9d-ae13-fcfd0f84929f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
