From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
xen-devel@lists.xenproject.org,
Doug Goldstein <cardoe@cardoe.com>,
"committers@xenproject.org" <committers@xenproject.org>
Subject: Re: [PATCH] automation: avoid duplicated builds of staging branch
Date: Sat, 22 Jul 2023 03:00:57 +0200 [thread overview]
Message-ID: <ZLsqSWXvwxBQK3NG@mail-itl> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2307211749270.3118466@ubuntu-linux-20-04-desktop>
[-- Attachment #1: Type: text/plain, Size: 2812 bytes --]
On Fri, Jul 21, 2023 at 05:49:49PM -0700, Stefano Stabellini wrote:
> On Sat, 22 Jul 2023, Marek Marczykowski-Górecki wrote:
> > On Fri, Jul 21, 2023 at 05:14:01PM -0700, Stefano Stabellini wrote:
> > > 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.
> >
> > Well, if that's the case, either it got manually enabled on those 4 (?)
> > forks, or those are using something else for mirroring the staging
> > branch (in which case, the setting would not help). I can't see this
> > part of the settings in other's repositories, so I don't know.
>
> Do you know the name of those 4 forks? I can help figure it out.
Looking at "activity" view on gitlab, I see those:
https://gitlab.com/xen-project/fusa/xen-integration
https://gitlab.com/xen-project/people/olkur/xen
https://gitlab.com/xen-project/people/andyhhp/xen
There are few more that have staging branch almost up to date, but seems
to be pushed manually (based on it being not fully up to date) and less
often.
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-07-22 1:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 13:09 [PATCH] automation: avoid duplicated builds of staging branch Marek Marczykowski-Górecki
2023-07-17 13:14 ` Andrew Cooper
2023-07-17 14:08 ` Marek Marczykowski-Górecki
2023-07-21 23:42 ` Stefano Stabellini
2023-07-22 0:07 ` Marek Marczykowski-Górecki
2023-07-22 0:14 ` Stefano Stabellini
2023-07-22 0:24 ` Marek Marczykowski-Górecki
2023-07-22 0:49 ` Stefano Stabellini
2023-07-22 1:00 ` Marek Marczykowski-Górecki [this message]
2023-07-22 1:18 ` Stefano Stabellini
2023-07-24 8:27 ` Oleksii
2023-07-24 20:58 ` Stefano Stabellini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZLsqSWXvwxBQK3NG@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=andrew.cooper3@citrix.com \
--cc=cardoe@cardoe.com \
--cc=committers@xenproject.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.