I saw it as well. Put on my personal list for the next meeting. But this is the better approach.

I don't know much about Zuul, yet. But having a large stack of interdependent packages, I certainly see a general benefit. To be discussed next meeting...

Here's some info I found on Zuul usage for packages:

https://fedoraproject.org/wiki/Zuul-based-ci#Attach_packaging_jobs_for_a_distgit_repository_on_src.fedoraproject.org

I opened a PR to add all packages from #528 to Zuul.

I'm reopening this. This time I'd like to add all packages neuro-sig has commit rights on. I think it is very helpful having a set of tests run for every PR. The installability test (example) would have saved my butt at least twice last week and another two or so times in the weeks before that when I was going through FTBFS/FTI bugs.

I followed the process lined out in How to add / maintain your packages list. I'm not sure though, the file should be replaced as outlined in the README of the zuul-config-generator tool.

I'll figure that out and, if nobody objects, submit a PR to have all our packages included sometime next week or following our next meeting, if we'd like to discuss further. It looks like this has to be done regularly to keep the list of packages up to date.

Sure, it'll be great to have zuul on all our packages. I have a script here that gets a list of all neuro-sig packages if you need it:

https://pagure.io/neuro-sig/NeuroFedora/blob/main/f/package-list/get-package-list.sh

I'm using zuul-config-generator as per their instructions. Thanks for the script nonetheless.

I'm not sure though, the file should be replaced as outlined in the README of the zuul-config-generator tool.

It looks like the script merges the packages from your command-line “query” with those already in the existing config file, so replacing does work. At least, that’s what I found when using the script to add my new packages to Zuul. It did seem to want to add a few packages that I had committed to via PR’s but didn’t have current permissions on, which was odd. It still saved a lot of time, so thanks for mentioning it.

Glad to be of help and thanks for the nudge!

I know where I went wrong. I didn't see the link between the two repositories: fedora-project-config and zuul-config-generator. I did submit a PR for fedora-project-config as documented in this ticket:

I opened a PR to add all packages from #528 to Zuul.

But that was hand edited.

It's done now. I submitted all neuro-sig packages: https://pagure.io/fedora-project-config/pull-request/294

PR has been merged.

Since our list of packages is ever evolving, we need to repeat that process every once in a while.

I have submitted https://pagure.io/fedora-project-config/pull-request/312 a couple of days ago to include all newly added neuro-fedora packages.

This ticket has been migrated to the forgejo instance. Please find the new ticket here
https://forge.fedoraproject.org/neuro/NeuroFedora//issues/533