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 methods for retrieving running jobs #2725

Open
3 tasks
Tracked by #5
mfocko opened this issue Feb 19, 2025 · 0 comments
Open
3 tasks
Tracked by #5

Implement methods for retrieving running jobs #2725

mfocko opened this issue Feb 19, 2025 · 0 comments
Labels
area/general Related to whole service, not a specific part/integration. complexity/single-task Regular task, should be done within days. kind/feature New feature or a request for enhancement.

Comments

@mfocko
Copy link
Member

mfocko commented Feb 19, 2025

Implement methods that yield respective jobs to be cancelled, i.e., after retriggering a Copr build, we should get a list of running Copr builds associated with the previous trigger.

Warning

There is a possible issue with retriggering via comments (as they are not the same trigger, i.e., there would be a need to map the PR ID / current commit hash to the latest running builds/tests with the same commit hash).

Considering packit/packit#2534, the methods should return lists of Copr build IDs or Testing Farm request IDs.

For the sake of this card, do not consider subsequent jobs. It will be handled by a follow-up issue.

TODO

  • Parse the revisions (commit hashes) from the respective events
    • GitHub
    • GitLab
      • For MRs there should be an oldrev attribute
      • Pushes contain before and after in the same fashion as the GitHub
  • Implement method that provides already running Copr build for the preceding event
  • Implement method that provides already running Testing Farm runs for the preceding event
@mfocko mfocko added area/general Related to whole service, not a specific part/integration. complexity/single-task Regular task, should be done within days. kind/feature New feature or a request for enhancement. labels Feb 19, 2025
@mfocko mfocko moved this from new to priority-backlog in Packit Kanban Board Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/general Related to whole service, not a specific part/integration. complexity/single-task Regular task, should be done within days. kind/feature New feature or a request for enhancement.
Projects
Status: priority-backlog
Development

No branches or pull requests

1 participant