Re: Buildbot Try artifact expiration
On 9/29/16 5:15 PM, dmitch...@mozilla.com wrote: Op maandag 26 september 2016 15:28:56 UTC-4 schreef Boris Zbarsky: OK. In my experience, it's very useful to have logs available longer than just two weeks. If nothing else, some of the things that start trying to look at them only happen about once a week Is that still true when limited just to try? Yes. I kind of pity any automation that's reading logs from try jobs, since it's such a collection of crazy failing pushes.. Sure. And stuff doesn't get starred intermittent correctly on try very much. But it does happen some, and can be useful. Is there a different expiration interval that would be more appropriate for logs? 28 days? If it's easy to do that, it would be quite helpful, yes. For my purposes 28 days should be pretty good. -Boris ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Buildbot Try artifact expiration
Op maandag 26 september 2016 15:28:56 UTC-4 schreef Boris Zbarsky: > OK. In my experience, it's very useful to have logs available longer > than just two weeks. If nothing else, some of the things that start > trying to look at them only happen about once a week Is that still true when limited just to try? I kind of pity any automation that's reading logs from try jobs, since it's such a collection of crazy failing pushes.. Is there a different expiration interval that would be more appropriate for logs? 28 days? Dustin ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Buildbot Try artifact expiration
On 9/23/16 2:53 PM, gar...@mozilla.com wrote: For taskcluster, starting in May, the entire task would be expired, including any output from it (artifacts, logs, etc). OK. In my experience, it's very useful to have logs available longer than just two weeks. If nothing else, some of the things that start trying to look at them only happen about once a week -Boris ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Buildbot Try artifact expiration
> Just to be clear, what counts as "artifacts" here? The actual build? > The log? All of the above? For taskcluster, starting in May, the entire task would be expired, including any output from it (artifacts, logs, etc). If you look at a taskcluster task on try from August you will see that the task no longer exists. However, if this default was ever a problem for a certain task, or if you want tasks from your push to try to live for longer, all of the task definitions live in tree, and you can update them to have a different default expiration. Here is an example from our task transform logic. Basically the task would need to define "expires-after". https://dxr.mozilla.org/mozilla-central/source/taskcluster/taskgraph/transforms/task.py?q=taskcluster%2Ftaskgraph%2Ftransforms%2Ftask.py_type=direct#485 For buildbot try jobs, expiring artifacts older than 14 days is any file that buildbot or mozharness created using TaskCluster. I'm not sure if buildbot itself is doing anything to upload through TaskCluster, but mozharness based actions definitely do. This could include logs. What we are wanting to do is retroactively expire buildbot try artifacts (which may include some logs) older than 14 days, as well as expire TaskCluster try artifacts created before May that are still lingering around before we made this default behavior. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Buildbot Try artifact expiration
On 9/22/16 2:52 PM, gar...@mozilla.com wrote: In May it was decided that artifacts for try jobs running in TaskCluster should expire after 14 days. Just to be clear, what counts as "artifacts" here? The actual build? The log? All of the above? There may be value for keeping logs longer than that... -Boris ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Buildbot Try artifact expiration
In May it was decided that artifacts for try jobs running in TaskCluster should expire after 14 days. This has greatly reduced the amount of try artifacts that we keep within s3 and we are looking to make the same changes to buildbot try artifacts that were uploaded using TaskCluster. Bug 1303214 has been created to make this the new default when using mozharness to upload artifacts. In the meantime the TaskCluster team would like to move forward with retroactively expiring buildbot try artifacts within S3 that are older than 14 days. Note: this is only for Try artifacts that were created and uploaded using mozharness and stored within TaskCluster (but are actually buildbot jobs). Ideally we should be able to keep default expiration times for Try artifacts consistent between buildbot and TaskCluster and so far we have found 14 days to be an acceptable default. Please let me know if you see an issue with this and we can discuss. A final notice will be sent prior to forced expiration if there are no objections. -Greg ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
