Use automotive sig coprs for packit tasks

[lsm5]

          > > > As a first step, maybe it's worth switching Packit copr tasks to use the automotive-sig coprs in https://github.com/containers/qm/blob/main/.packit.yaml . Currently, it uses `rhcontainerbot/packit-builds` and `rhcontainerbot/qm` coprs.

@lsm5 are you looking to this task? Should we create an issue in GH?

@dougsland I'd rather someone else more active on qm take the lead here.

@lsm5 could you please just open an issue against QM with your view and steps which we should approach? I can take the lead to make it happen.

Originally posted by @dougsland in #122 (comment)

[lsm5]

1. Create a couple of coprs in the automotive sig group. One for running builds to test every PR, and another for builds after a PR is committed to main.
2. Update .packit.yaml to use those 2 coprs for trigger: pull_request and trigger: commit jobs.

[lsm5]

@dougsland does that help ^ ?

[dougsland]

@dougsland does that help ^ ?

Sure, it's a start. :-)

[dougsland]

@pypingou could you please help us with the automotive sig ?

[dougsland]

@Yarboa could you please review this one as you are leading the packit effort now ?

[Yarboa]

Sure, let me check

[lsm5]

1. Create a couple of coprs in the automotive sig group. One for running builds to test every PR, and another for builds after a PR is committed to main.
2. Update .packit.yaml to use those 2 coprs for trigger: pull_request and trigger: commit jobs.

Update: it's probably better to create just 1 copr in the automotive sig to host packages built after commit to main branch. For trigger: pull_request tasks, you can just use the ephemeral copr that packit creates.

[Yarboa]

@dougsland
looking here https://copr.fedorainfracloud.org/groups/g/centos-automotive-sig/coprs/
I do not see qm copr,
Once you create qm project it is easy to change owner and project in packit.yaml

[dougsland]

@sandrobonazzola do you have the permission to create QM under centos-automotive-sig/coprs?

[sandrobonazzola]

Yes, i have permission. Do you need a new repo or do you think qm can fit into any of the existing ones?

[dougsland]

Yes, i have permission. Do you need a new repo or do you think qm can fit into any of the existing ones?

I would go with a new one but I am okay with existing one. What's your suggestion?

[sandrobonazzola]

if it's for building on every commit I would suggest to go with a new copr like bluechi did (https://copr.fedorainfracloud.org/coprs/g/centos-automotive-sig/bluechi-snapshot/) so something like qm-snapshot.

For tagged releases, I assume they'll eventually land in Automotive SIG/AutoSD so I would suggest to push tagged builds to https://copr.fedorainfracloud.org/coprs/g/centos-automotive-sig/next/

[dougsland]

if it's for building on every commit I would suggest to go with a new copr like bluechi did
(https://copr.fedorainfracloud.org/coprs/g/centos-automotive-sig/bluechi-snapshot/) so something like qm -snapshot.

This one seems more appropriate. Thanks Sandro!

[sandrobonazzola]

So, are you going to use bluechi-snapshot or do you want me to create qm-snapshot for you?

[dougsland]

So, are you going to use bluechi-snapshot or do you want me to create qm-snapshot for you?

Could you please create qm-snapshot? I believe for now, access will be required for me (devel), yariv (qe) and you as centos maint.

[sandrobonazzola]

COPR repository created, please request permission for it at https://copr.fedorainfracloud.org/coprs/g/centos-automotive-sig/qm-snapshot/permissions/

[dougsland]

COPR repository created, please request permission for it at https://copr.fedorainfracloud.org/coprs/g/centos-automotive-sig/qm-snapshot/permissions/

requested, thanks a lot @sandrobonazzola ! Kudos!

@Yarboa PTAL

[Yarboa]

COPR repository created, please request permission for it at https://copr.fedorainfracloud.org/coprs/g/centos-automotive-sig/qm-snapshot/permissions/

requested, thanks a lot @sandrobonazzola ! Kudos!

@Yarboa PTAL

Thank you @sandrobonazzola 🚀