[gentoo-dev] Repository mirrors & CI are looking for a new "maintainer"

[gentoo-dev] Repository mirrors & CI are looking for a new "maintainer"

[Michał Górny]

Hi, everyone.

TL;DR: I need someone to take over the job of minimal "maintenance" work
around repo mirrors & CI.  I can still do the needed code changes, I
just need replacement for stuff like filing bugs and taking care of
immediate issues.


I've started the repo-mirror-ci project back in 2015 to provide QA
checks for the Gentoo repositories (as listed in repositories.xml). 
Originally, it was supposed to run repoman (later: pkgcheck) on all
repos.  You can guess how that went.

Fast-forward, the project roughly broke into three somewhat
complementary parts:

1) Repository mirrors that sync, do basic "is it working" checks
and generate md5-cache (which also catches some ebuild problems) for all
repos.

2) Gentoo CI that runs pkgcheck against ::gentoo.

3) Pull request CI that runs pkgcheck against pull requests on GitHub.

Nowadays, everything is running on Gentoo Infra, lots of things are
automated but it still requires some manual maintenance.  Most notably,
this includes:

a. periodically running a script to file or update bugs about problems
with overlays,

b. pinging overlay maintainers and removing obsolete overlays if
necessary (this part seems to have been partially taken over),

c. occasionally dealing with weird failures blocking repos pipeline --
usually through adding repos to bla... I mean, blocklist until I manage
to fix the scripts.


While admittedly this isn't that much work, I no longer wish to do it. 
I still feel responsible for setting this up, so I'll do my best to keep
the code working but I need somebody else to do the maintenance work.

If you're interested, please ping me on IRC and I'll give you a quick
run-around and add you where necessary.  I don't think you need strictly
to be a dev but you'll need editbugs.

-- 
Best regards,
Michał Górny

Re: [gentoo-dev] Repository mirrors & CI are looking for a new "maintainer"

[Alec Warner]

On Thu, Mar 24, 2022 at 3:41 PM Michał Górny <mgorny@gentoo.org> wrote:
>
> Hi, everyone.
>
> TL;DR: I need someone to take over the job of minimal "maintenance" work
> around repo mirrors & CI.  I can still do the needed code changes, I
> just need replacement for stuff like filing bugs and taking care of
> immediate issues.
>
>
> I've started the repo-mirror-ci project back in 2015 to provide QA
> checks for the Gentoo repositories (as listed in repositories.xml).
> Originally, it was supposed to run repoman (later: pkgcheck) on all
> repos.  You can guess how that went.
>
> Fast-forward, the project roughly broke into three somewhat
> complementary parts:
>
> 1) Repository mirrors that sync, do basic "is it working" checks
> and generate md5-cache (which also catches some ebuild problems) for all
> repos.
>
> 2) Gentoo CI that runs pkgcheck against ::gentoo.

Happy to take this.

>
> 3) Pull request CI that runs pkgcheck against pull requests on GitHub.

Happy to take this too.

Both are part of work we would need to do to migrate CI to gitlab
(should we eventually move stuff to gitlab.)

>
> Nowadays, everything is running on Gentoo Infra, lots of things are
> automated but it still requires some manual maintenance.  Most notably,
> this includes:
>
> a. periodically running a script to file or update bugs about problems
> with overlays,
>
> b. pinging overlay maintainers and removing obsolete overlays if
> necessary (this part seems to have been partially taken over),
>
> c. occasionally dealing with weird failures blocking repos pipeline --
> usually through adding repos to bla... I mean, blocklist until I manage
> to fix the scripts.
>
>
> While admittedly this isn't that much work, I no longer wish to do it.
> I still feel responsible for setting this up, so I'll do my best to keep
> the code working but I need somebody else to do the maintenance work.
>
> If you're interested, please ping me on IRC and I'll give you a quick
> run-around and add you where necessary.  I don't think you need strictly
> to be a dev but you'll need editbugs.
>
> --
> Best regards,
> Michał Górny
>
>

Re: [gentoo-dev] Repository mirrors & CI are looking for a new "maintainer"

[Michał Górny]

On Thu, 2022-03-24 at 23:41 +0100, Michał Górny wrote:
> If you're interested, please ping me on IRC and I'll give you a quick
> run-around and add you where necessary.  I don't think you need strictly
> to be a dev but you'll need editbugs.

laumann will be taking care of the repo reports from now on.  Big
thanks!

Unfortunately, the cheap scripts I've made are not suitable for being
used by more than one person (they rely on local database), so thanks
to everyone else who could be potentially interested in doing this.

-- 
Best regards,
Michał Górny

Re: [gentoo-dev] Repository mirrors & CI are looking for a new "maintainer"

[Michał Górny]

On Thu, 2022-03-24 at 17:31 -0700, Alec Warner wrote:
> On Thu, Mar 24, 2022 at 3:41 PM Michał Górny <mgorny@gentoo.org> wrote:
> > 
> > Hi, everyone.
> > 
> > TL;DR: I need someone to take over the job of minimal "maintenance" work
> > around repo mirrors & CI.  I can still do the needed code changes, I
> > just need replacement for stuff like filing bugs and taking care of
> > immediate issues.
> > 
> > 
> > I've started the repo-mirror-ci project back in 2015 to provide QA
> > checks for the Gentoo repositories (as listed in repositories.xml).
> > Originally, it was supposed to run repoman (later: pkgcheck) on all
> > repos.  You can guess how that went.
> > 
> > Fast-forward, the project roughly broke into three somewhat
> > complementary parts:
> > 
> > 1) Repository mirrors that sync, do basic "is it working" checks
> > and generate md5-cache (which also catches some ebuild problems) for all
> > repos.
> > 
> > 2) Gentoo CI that runs pkgcheck against ::gentoo.
> 
> Happy to take this.
> 
> > 
> > 3) Pull request CI that runs pkgcheck against pull requests on GitHub.
> 
> Happy to take this too.
> 
> Both are part of work we would need to do to migrate CI to gitlab
> (should we eventually move stuff to gitlab.)
> 

Err but I just said these need no maintenance?  But I'll keep that
in mind if there's any work to do.

And yes, I'd agree that if we decide to run GitLab long term, then it'd
be nice to move CI there using some standard pipelines.

-- 
Best regards,
Michał Górny