action #97028
closed
openqa-clone-job: Pass id of cloned job as setting
Added by tinita over 3 years ago.
Updated about 3 years ago.
Category:
Feature requests
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
- Copied from action #96959: Job hooks trigger investigate jobs for passed/soft-failed size:M added
- Target version changed from Ready to future
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 :)
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.)
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?
- Status changed from New to In Progress
- Assignee set to osukup
- Status changed from In Progress to Resolved
Also available in: Atom
PDF