Add ability to backup selected jobs/tests results outside of o.s.d/o.o.o
For QAM is important to store results from test for whole lifetime of product. Outside of openQA instance.
Wee need run some internal tools over results.
#1 Updated by okurz over 3 years ago
- Category set to Feature requests
You may want to use https://progress.opensuse.org/projects/openqav3/wiki#feature-requests as a template for this feature request. Can you state which part of test results of a job you want to backup? I am not sure if this needs any changes on openQA side. You can access job results over webui as well as API which should give all the necessary information, e.g. try
curl -s https://openqa.opensuse.org/api/v1/jobs/234123 to have results in JSON. Try
https://openqa.opensuse.org/help to see all available routes.
Probably a script on your side is a better solution here.
#2 Updated by RBrownSUSE over 3 years ago
Oli, your Template is not an approved process by the openQA community, nor approved by either of the project leads (Coolo and myself)
Please remove the wiki article, or at less stop demanding people use a process which you concocted on your own
Consider people's feature requests on THIER own merits, not just your own criteria.
#7 Updated by rdodopoulos about 3 years ago
@rdodopoulos - it helps if the instance you're fetching the job from actually has that job. openqa.opensuse.org's max job id is 313196
I thought it could predict future results but I guess not :(
https://openqa.suse.de/api/v1/jobs/653953/ returns the settings instead of the results. Is there something that can provide the results in a way that Panos' dbaq does? If not, should we include his script in os-autoinst/openQA/scipt/ ?
#8 Updated by okurz about 3 years ago
@rdodopoulos I think dbaq provides a nice way to access the data. The api provides another. Both way can not provide everything that the database of openQA knows about the job including all screenshots, logs, relations, settings, etc. There was the idea to provide a more or less full representation of the jobs result page in json but we don't have that yet. I am not sure what you want to achieve and what data exactly is necessary for that. Also for this ticket the use case is unclear to me (hence comment #1 which was apparently misunderstood) and there is no progress. I think dbaq should stay in it's own repository as it is a client tool which interacts with openQA but does not need to be developed in the same repository with it. You might also try other options - depending on your specific needs - e.g. openQA-python-client and openqa_review. The latter is also in openSUSE Tumbleweed and Leap 42.2, a simple
zypper in python-openqa_review away :-)
#15 Updated by szarate almost 2 years ago
There is a PR: https://github.com/os-autoinst/openQA/pull/1571
Currently there is a problem addressing a request of making the download of assets an opt-in with a size limit.
When setting max_size_message in the UA, it works if the file is above 128K but otherwise if max_message_size is set under under that, it seems to fail in my local branch.