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

Implement installability check for Packit as a Fedora dist-git CI #2712

Open
Tracked by #2692
lachmanfrantisek opened this issue Feb 11, 2025 · 0 comments
Open
Tracked by #2692
Labels
area/fedora Related to Fedora ecosystem complexity/single-task Regular task, should be done within days. demo The issue is worth demoing. Don't forget to finish your work by presenting the results to others! gain/high This brings a lot of value to (not strictly a lot of) users. impact/high This issue impacts multiple/lot of users. kind/feature New feature or a request for enhancement.

Comments

@lachmanfrantisek
Copy link
Member

lachmanfrantisek commented Feb 11, 2025

Run installability check for successful Koji scratch builds on Fedora dist-git pull-requests.

You can also consider defining another plan and putting it e.g. here. Maybe also making the upstream one usable both upstream and downstream.

This is a part of the phase 2 of #2692

@lachmanfrantisek lachmanfrantisek added area/fedora Related to Fedora ecosystem complexity/single-task Regular task, should be done within days. demo The issue is worth demoing. Don't forget to finish your work by presenting the results to others! gain/high This brings a lot of value to (not strictly a lot of) users. impact/high This issue impacts multiple/lot of users. kind/feature New feature or a request for enhancement. labels Feb 11, 2025
@lachmanfrantisek lachmanfrantisek moved this from new to priority-backlog in Packit Kanban Board Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/fedora Related to Fedora ecosystem complexity/single-task Regular task, should be done within days. demo The issue is worth demoing. Don't forget to finish your work by presenting the results to others! gain/high This brings a lot of value to (not strictly a lot of) users. impact/high This issue impacts multiple/lot of users. kind/feature New feature or a request for enhancement.
Projects
Status: priority-backlog
Development

No branches or pull requests

1 participant