On Thu, Oct 11, 2018 at 11:46:14AM -0300, Antonio Terceiro wrote:
Hello,
On Thu, Oct 11, 2018 at 03:39:53PM +0200, Vincent Guittot wrote:
On Thu, 11 Oct 2018 at 15:13, Martin Stadler martin.stadler@linaro.org wrote:
On Thu, 11 Oct 2018 at 11:24, Ryan Harkin ryan.harkin@linaro.org wrote:
On Thu, 11 Oct 2018 at 10:35, Milosz Wasilewski milosz.wasilewski@linaro.org wrote:
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.
I don't need to keep my results forever. But what would be nice is to be able to keep 180 days OR n sets of data.
Similar item here, what I do need is to keep iterave data sets from each releae of the ERP. This doesn't mean that we need all test runs, just the final tests, for each server platfrom, for each release of the ERP.
I understand that this will make things more complex, but that said, this is a complex issue and just having X days worth of data is not going to be useful, as I am sure you can understand.
+1 for the being able to set a size.
Even if we do't want to save results forever, 180 days seems to be far too short. In our PMWG case, It seems reasonable to keep data as long as the tested kernel is maintained so we can make comparison across the whole life. We are more in the range of 2 years and even 6 years as announced for v4.4 at last connect But we probably don't want to keep all results but only a subset of them
Thanks for everyone's feedback. So my plan to address your concerns is the following:
allow the cleanup to be disabled completely by setting the number of days to -1. This can be used as a simple solution for projects that have new builds at a low frequency.
add a `keep forever` flag to build objects, that can be set using the REST API. This way each project can mark exactly which builds they want to keep, without needing to hardcode any specific logic in squad.
For LKFT we're still discussing what our policy should be for data retention. We link into qa-reports and lava in bugs and public mailing lists posts, and so our task is to assess the impact of such links breaking over time.
Logistically, will there be time to set this value after this feature is released, but before the first purge occurs, so that we will not lose data as a part of the deployment? We will surely want more than 180 days, but we're trying to decide if 365 is sufficient.
Dan