On Fri, Jun 16, 2023 at 6:42 AM Stephen Gallagher <sgall...@redhat.com>
wrote:

> == Open Questions ==
> 1) For the "canary" Fedora ELN rebuild, we have two choices on how to
> select the git hash to be built for each package in the ELN list:
>
> Approach 1 (Rawhide-style):
> 1. Clone each package
> 2. Check for the existence of the `eln` branch.
>   a. If the `eln` branch exists, build from the HEAD of that branch
> into the side-tag.
>   b. Otherwise, build from the HEAD of the `rawhide` branch into the
> side-tag.
>
> Approach 2 (Conservative-style):
> 1. Query Koji for the latest-tagged build of each package in Fedora ELN
> 2. Interrogate the build task of that build for the git hash
> 3. Build that git hash into the side-tag.
>
> Approach 2 is more heavyweight, relying on a lot of Koji queries
> back-and-forth, whereas Approach 1 will pick up changes that have
> appeared in Rawhide since the last build (which is more in line with
> how Fedora's mass-rebuilds work). I'm personally leaning towards
> Approach 2, but I'm open to good arguments either way.
>

Sorry for being late with this, but I thought I'd already sent this.

I'd like to go with Approach 2 (Conservative-style)
I've got a python script that grabs the githash for various builds.
Although the initial run takes a couple of hours, after that it's fairly
quick.
It would make it possible to build using the ELN build source githash.

In the long run, I believe it takes less time to get the githash rather
than pulling down the git repos.
It's also something the can be pre-staged, then just run the script right
before you run the mass rebuild, to get the latest.

Troy
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to