Re: [PATCH] automation: avoid duplicated builds of staging branch

[Stefano Stabellini <sstabellini@xxxxxxxxxx>]

On Sat, 22 Jul 2023, Marek Marczykowski-Górecki wrote:
> On Fri, Jul 21, 2023 at 04:42:11PM -0700, Stefano Stabellini wrote:
> > On Mon, 17 Jul 2023, Marek Marczykowski-Górecki wrote:
> > > On Mon, Jul 17, 2023 at 02:14:14PM +0100, Andrew Cooper wrote:
> > > > On 17/07/2023 2:09 pm, Marek Marczykowski-Górecki wrote:
> > > > > "staging" branch is mirrored (automatically or manually) to several
> > > > > repositories. Avoid building it several times to not waste runner
> > > > > resources.
> > 
> > Hi Marek,
> > 
> > Let me try to understand the use-case a bit better. You would like the
> > following "staging" branch to run a full pipeline:
> > https://gitlab.com/xen-project/xen
> > 
> > But if someone under xen-project/people is mirroring
> > https://gitlab.com/xen-project/xen, this patch is attempting to skip the
> > additional pipeline. For instance, if I am mirroring staging in my
> > personal repo:
> > 
> > https://gitlab.com/xen-project/people/sstabellini/xen
> > 
> > We are skipping the additional pipeline there.
> 
> Yes.
> 
> > Is that correct? If so, it would be easier to ask everyone to make sure
> > they have "Trigger pipelines for mirror updates" unselected:
> > 
> > https://docs.gitlab.com/ee/user/project/repository/mirror/pull.html#trigger-pipelines-for-mirror-updates
> 
> If that's set in gitlab as pull mirror (instead of push from somewhere
> else), then that indeed may be enough. But is it really in all those
> cases?

Yes, it is an option in the pull mirror, by default should be unselected
I believe.