action #67888
closed
openqa-clone-custom-git-refspec cannot trigger a job that has no vars.json
Added by Xiaojing_liu almost 4 years ago.
Updated almost 4 years ago.
Category:
Feature requests
Description
User story¶
There are two jobs: parent job and child job. When parent job fails, the child job is skipped, so there is no vars.json file in child job.
Then users trigger the child job by using openqa-clone-custom-git-refspec to check their test code, it fails because could not find the vars.json.
Acceptance criteria¶
- AC1:
openqa-clone-custom-git-refspec should trigger the child and parent job successfully.
Workaround¶
use openqa-clone-job to do that, it needs to specify CASEDIR
I make a mistake about the format. Did not find a button to modify it. So add some comments here.
Workaround:
use openqa-clone-job to do that, need to specify CASEDIR=xxx
- Description updated (diff)
Fixed the description. There is a button "Edit" on top right to edit a ticket and another "Edit" button next to "Description" of the ticket
- Status changed from New to Feedback
- Assignee set to okurz
https://github.com/os-autoinst/openQA/pull/3170 to cover this problem as well as whenever anyone calls openqa-clone-custom-git-refspec on scheduled, running, very old or non-existant jobs.
Potentially there is the alternative to let openqa-clone-custom-git-refspec lookup alternative jobs but trying to be too smart can go wrong easily :)
okurz wrote:
https://github.com/os-autoinst/openQA/pull/3170 to cover this problem as well as whenever anyone calls openqa-clone-custom-git-refspec on scheduled, running, very old or non-existant jobs.
Potentially there is the alternative to let openqa-clone-custom-git-refspec lookup alternative jobs but trying to be too smart can go wrong easily :)
Thanks for handling this. I think this error message is very clear for users.
- Status changed from Feedback to Resolved
Also available in: Atom
PDF