One approach we've taken when considering changes to the routes used is to play in the 'garbage.' prefix. You can see the results of earlier experiments there:
https://tools.taskcluster.net/index/#garbage/garbage Regarding your proposal, I find the word 'nightly' overloaded, and it needs more context to make sense. There are lots of 'nightly' builds, but only one 'nightly' channel (for Firefox anyway). So "gecko.v2.firefox.win64-opt.nightly.latest" isn't clear to me at first glance. I'm curious what others think though. On Tue, Dec 1, 2015 at 11:46 AM, Julien Wajsberg <jwajsb...@mozilla.com> wrote: > hi, > > Because we have an index, it's now very easy to add new routes. I think > it would be a lot more user-friendly to have an index that starts with > the product name ("firefox" for example). > > For example: "gecko.v2.firefox.win64-opt.nightly.latest" instead of > "gecko.v2.mozilla-central.nightly.latest.firefox.win64-opt > < > https://tools.taskcluster.net/index/artifacts/#gecko.v2.mozilla-central.nightly.latest.firefox/gecko.v2.mozilla-central.nightly.latest.firefox.win64-opt > >". > Going from the most general to the most specific. > Using an index that starts with "mozilla-central" is really technical > and does not make things easy to find :/ Even if it can be good for > automated tools. > > Fortunately now it's not either one or the other, we can have both. But > before filing a bug, I'd like to know if the general population thinks > it's a good idea. > > -- > Julien > > Le 30/11/2015 21:43, Chris AtLee a écrit : > > 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 > > _______________________________________________ > > 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 > > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
