Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Packit as a CI for Fedora dist-git pull requests #2453

Open
1 task
lachmanfrantisek opened this issue Jul 1, 2024 · 0 comments
Open
1 task

Packit as a CI for Fedora dist-git pull requests #2453

lachmanfrantisek opened this issue Jul 1, 2024 · 0 comments
Labels
complexity/epic Lost of work ahead, planning/design required.

Comments

@lachmanfrantisek
Copy link
Member

lachmanfrantisek commented Jul 1, 2024

Since Fedora-CI is being deprecated and Zuul is being transferred to the Testing Farm for the limited time for maintenance, Packit can take this role and help Fedora there.

Why?

  • Our users ask us quite regularly to have the same UX upstream/downstream and to have full workflow covered by PAckit.
  • We already have most of the code/integration/events ready nevertheless.
  • We are currently working on Research Packit reverse-dependency checks #2361 and as part of that, support for dist-git PRs would be needed nevertheless.
  • It looks to me like there is not much will/time to maintain Fedora-CI/Zuul-based solution so would be nice of us to help here. Without proper CI, Packit-proposed pull-requests do not make much sense.

Thinks to consider/discuss/think about:

  • Have it as part of the current instance? Or a separate instance?
  • What about configs? Should we add support for global config or even (really not sure about this) run automatically for all the packages? (Might be more a political discussion than a technical one..;)
  • Should we move to the Fedora OpenShift?

Tasks:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity/epic Lost of work ahead, planning/design required.
Projects
Status: new
Development

No branches or pull requests

1 participant