Project

General

Profile

Actions

action #168013

closed

coordination #58184: [saga][epic][use case] full version control awareness within openQA

coordination #152847: [epic] version control awareness within openQA for test distributions

Only make one api call in openqa-advanced-retrigger-jobs

Added by tinita 7 months ago. Updated 6 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2024-10-09
Due date:
% Done:

0%

Estimated time:

Description

Motivation

Currently openqa-advanced-retrigger-jobs makes one API call to /jobs/id/restart per job.
The /jobs/restart endpoint can already handle multiple jobs. We should use that.
Especially now since we trigger a git_clone for every restart event, see #164898.

Also we can now use the new comment feature, so also the optional comment API call can be replaced.

Suggestions

  • Improve script in general while implementing this, e.g. offer helpful output in dry_run mode what SQL would be executed

Related issues 2 (1 open1 closed)

Related to openQA Project (public) - action #164898: Replace fetchneedles with a minion job for the regular update of git repos size:MResolvedtinita

Actions
Related to openQA Project (public) - action #160889: [retro] Scripts used to retrigger jobs are difficult to use size:SWorkable2024-05-24

Actions
Actions

Also available in: Atom PDF