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
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 lim
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 thing
> 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
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 th
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 1303
6 matches
Mail list logo
