action #97028
closedopenqa-clone-job: Pass id of cloned job as setting
0%
Description
Updated by tinita over 3 years ago
- Copied from action #96959: Job hooks trigger investigate jobs for passed/soft-failed size:M added
Updated by okurz over 3 years 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 :)
Updated by mkittler over 3 years 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.)
Updated by livdywan over 3 years 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-jobbecause it only works within an instance. This feature should however work across instances. (SoCLONED_FROMshould 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?
Updated by osukup about 3 years ago
- Status changed from New to In Progress
- Assignee set to osukup