QA » openQA Project

lansuse wrote:

`lan@localhost:~/work/openqa-job-retrigger-tool> /usr/share/openqa/script/client --host http://openqa.qa2.suse.asia --apibase / group_overview/20 limit_builds=1 undef lan@localhost:~/work/openqa-job-retrigger-tool> /usr/share/openqa/script/client --json-output --host http://openqa.qa2.suse.asia --apikey 81F4ED4794F6E574 --apisecret 3895BC8179CCA96

the host "openqa.qa2.suse.asia" is not publically reachable but I still suggest as a best practice to treat "apikey" and "apisecret" like your passwords and not post them in chat rooms or tickets or wiki pages.

The command line looks garbled. I assume the word "undef" should go into its own line and is the output you got? Can you try the command openqa-client --host http://openqa.qa2.suse.asia group_overview/20 get limit_builds=1 please?

no response, giving more time.

@lansuse please see my above question

Ok. So what you are doing with the parameter --apibase / is basically not using the intended web API at all but instead retrieve the web pages that are meant for consumption by browsers and human readers. If you want to have a machine readable representation of the "group overview" page in JSON format you can use for example

curl -s https://openqa.opensuse.org/group_overview/1.json

Both openqa-client and openqa-cli are not meant and not necessary to access these pages. Good enough?

Interesting. I do not know what are the conditions that make openqa-job-retrigger-tool consider candidates to retrigger. Have you looked into "auto-review" as documented on http://open.qa/docs/#_enable_custom_hook_scripts_on_job_done_based_on_result and presented over multiple channels (SUSE QE Tools workshop, one.suse.com, opensuse-factory@opensuse.org mailing list post, etc.). I think it can help you in a more consistent and maintainable way. Your workaround might work for the time being but keep in mind that only the routes on /api/v1 should be considered stable, the other routes can change with updates again.