What does that mean for jobs that have already run? My understanding is
that we can't change the expiration after the fact for them? Though I
guess that it's not an issue as long as we fix bug 1145300 prior to
shutting off publishing to archive.m.o?
I just want to avoid any gaps in nightly build coverage as the archived
builds are critical for regression hunting.
On 12/1/2015 9:49 AM, Chris AtLee wrote:
The expiration is currently set to one year, but we can (and should!)
change that for nightlies. That work is being tracked in
https://bugzilla.mozilla.org/show_bug.cgi?id=1145300
On Mon, Nov 30, 2015 at 7:00 PM, Ryan VanderMeulen <rya...@gmail.com> wrote:
On 11/30/2015 3:43 PM, Chris AtLee wrote:
The RelEng, Cloud Services and Taskcluster teams have been doing a lot of
work behind the scenes over the past few months to migrate the backend
storage for builds from the old "FTP" host to S3. While we've tried to
make
this as seamless as possible, the new system is not a 100% drop-in
replacement for the old system, resulting in some confusion about where to
find certain types of builds.
At the same time, we've been working on publishing builds to the
Taskcluster Index [1]. This service provides a way to find a build given
various different attributes, such as its revision or date it was built.
Our plan is to make the index be the primary mechanism for discovering
build artifacts. As part of the ongoing buildbot to Taskcluster migration
project, builds happening on Taskcluster will no longer upload to
https://archive.mozilla.org (aka https://ftp.mozilla.org). Once we shut
off
platforms in buildbot, the index will be the only mechanism for
discovering
new builds.
I posted to planet Mozilla last week [2] with some more examples and
details. Please explore the index, and ask questions about how to find
what
you're looking for!
Cheers,
Chris
[1] http://docs.taskcluster.net/services/index/
[2]
http://atlee.ca/blog/posts/firefox-builds-on-the-taskcluster-index.html
If I understand correctly, Taskcluster builds are only archived for one
year, whereas we have nightly archives going back 10+ years now. What are
our options for long-term archiving in this setup?
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
