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.

Sign up for GitHub

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

Jump to bottom

Packit as a Fedora dist-git CI: retriggering #2738

Open
1 task
nforro opened this issue Mar 3, 2025 · 1 comment
Open
1 task

Packit as a Fedora dist-git CI: retriggering #2738

nforro opened this issue Mar 3, 2025 · 1 comment
Labels
area/fedora-ci complexity/single-task Regular task, should be done within days. discuss discuss To be discussed within a team (usually on the so-called Architecture meeting next Thursday) 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

@nforro
Copy link
Member

nforro commented Mar 3, 2025

Description

Fedora CI reacts to [citest] comments and retriggers the scratch build and other tests, however Packit does not.

Importance

I would say not having retriggering is a blocker.

Workaround

  • There is an existing workaround that can be used until this is implemented.
@nforro nforro added the kind/feature New feature or a request for enhancement. label Mar 3, 2025
@LecrisUT
Copy link
Contributor

LecrisUT commented Mar 3, 2025

Should it also react to [citest] or /packit instead? I don't think [citest] is that widely documented that we would need exact mirroring, and it would be nice to have finer control of which job to re-trigger.

@nforro nforro added discuss discuss To be discussed within a team (usually on the so-called Architecture meeting next Thursday) complexity/single-task Regular task, should be done within days. impact/high This issue impacts multiple/lot of users. gain/high This brings a lot of value to (not strictly a lot of) users. labels Mar 4, 2025
@nforro nforro moved this from new to priority-backlog in Packit Kanban Board Mar 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/fedora-ci complexity/single-task Regular task, should be done within days. discuss discuss To be discussed within a team (usually on the so-called Architecture meeting next Thursday) 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
Packit Kanban Board
Status: priority-backlog
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nforro @LecrisUT