Project

General

Profile

action #97028

openqa-clone-job: Pass id of cloned job as setting

Added by tinita 4 months ago. Updated about 2 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2021-08-16
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

When cloning a job with openqa-clone-job, we don't see the original URL of the job which was cloned. This could be helpful sometimes.

Acceptance Criteria

AC1: openqa-clone-job will pass a new setting (e.g. CLONED_FROM) to the new job automatically


Related issues

Copied from openQA Project - action #96959: Job hooks trigger investigate jobs for passed/soft-failed size:MResolved2021-08-162021-09-23

History

#1 Updated by tinita 4 months ago

  • Copied from action #96959: Job hooks trigger investigate jobs for passed/soft-failed size:M added

#2 Updated by tinita 4 months ago

  • Target version changed from Ready to future

#3 Updated by okurz 4 months ago

discussed with tinita. I think the idea is good. As a potential alternative I had the idea that the /restart API route should take optional settings. In that case I thought I had that idea recorded in a ticket. Can't find it right now so it's recorded here :)

#4 Updated by mkittler 3 months ago

As a potential alternative I had the idea that the /restart API route should take optional settings. In that case I thought I had that idea recorded in a ticket. Can't find it right now so it's recorded here :)

The restart route is a different story. When restarting a job using that route openQA tracks that already and jobs show up as "cloned as" and "clone of". However, that route cannot be used by openqa-clone-job because it only works within an instance. This feature should however work across instances. (So CLONED_FROM should also contain the full URL and not just the job ID.)

#5 Updated by cdywan 3 months ago

mkittler wrote:

As a potential alternative I had the idea that the /restart API route should take optional settings. In that case I thought I had that idea recorded in a ticket. Can't find it right now so it's recorded here :)

The restart route is a different story. When restarting a job using that route openQA tracks that already and jobs show up as "cloned as" and "clone of". However, that route cannot be used by openqa-clone-job because it only works within an instance. This feature should however work across instances. (So CLONED_FROM should also contain the full URL and not just the job ID.)

Is that the only constraint? What if we swap out the route depending on wether the instance is the same?

#6 Updated by osukup about 2 months ago

  • Status changed from New to In Progress
  • Assignee set to osukup

#7 Updated by osukup about 2 months ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF