Hi,
Getting the output of 'email' API for the build usually takes a long
time. In some cases we're close to hitting the 30 seconds timeout. I
think the timeout is inevitable when there are a lot of results with
big number of changes. In order to avoid timeout, maybe the API
should do the work in background? This would work as follows
1. GET call to /api/builds/<id>/email
2. server creates a 'cashed report' object in database and returns URL
for it immediately to the user
3. in the background server adds a report generation task to the queue
4. using the URL received in 2) user is able to retrieve the final
results or check the progress
5. once the result is generated it can be a short lived object in the
database (removed after 1 day for example)
Is this the solution we should aim for? The downside is that it
requires active polling from the client side.
milosz
Hi,
Antonio proposed a patch that sets default data retention policy to
180 days. It can be changed for each project in qa-reports separately
(extended or shortened). We don't have an option to keep the data
forever. IMHO this is a good idea, but I wanted to ask whether you
have a need to keep your results forever.
The PR in question is here:
https://github.com/Linaro/squad/pull/370
milosz
Hi,
I release new version of SQUAD plugins yesterday but I'm not rolling
them out yet. I think it makes sense to make a new SQUAD release on
Monday and roll out both at the same time. Any objections?
milosz
