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

Move Fedora CI related code to a separate repository #2737

Open
2 tasks
Tracked by #2692
lbarcziova opened this issue Mar 3, 2025 · 2 comments
Open
2 tasks
Tracked by #2692

Move Fedora CI related code to a separate repository #2737

lbarcziova opened this issue Mar 3, 2025 · 2 comments
Labels
area/fedora-ci complexity/single-task Regular task, should be done within days. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related.

Comments

@lbarcziova
Copy link
Member

  • discuss the details with team
    • hardly could be a good inspiration
  • move the code to a dedicated repo

Some pointers:

@lbarcziova lbarcziova added kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related. area/fedora-ci complexity/single-task Regular task, should be done within days. labels Mar 3, 2025
@lachmanfrantisek
Copy link
Member

Just for reference, there are two related topics to this:

  • Having a new identity (either via a new FAS account(s) or via a different mechanism).
  • Moving into Fedora-infra OpenShift cluster.

@lbarcziova
Copy link
Member Author

+1, but I would say for the second point, it is more generally about having a separate deployment for the Fedora CI.

@nforro nforro moved this from new to priority-backlog in Packit Kanban Board Mar 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/fedora-ci complexity/single-task Regular task, should be done within days. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related.
Projects
Status: priority-backlog
Development

No branches or pull requests

2 participants