I was poking around a build from about 2 weeks ago and couldn't find the build directory or log from treeherder, but was able to track it down on archive.mozilla.org. I don't know where this fits in with the overall migration of ftp, there's probably a dupe somewhere around here.

Treeherder uses the log url specified in https://secure.pub.build.mozilla.org/builddata/buildjson/builds-4hr.js.gz , which is still saying ftp.m.o not archive.m.o

At this point ftp.m.o and archive.m.o are the same thing, since we haven't started the transition of files to S3. Could you provide an example of something present on archive but not on ftp ? I think this bug should naturally resolve itself. Once we cut over to the new upload hosts they'll return urls beginning with https://archive.mozilla.org instead of ftp, and builds-4hr will pass that on.

When I filed this I had builds/logs I couldn't find on ftp, but could on archive.m.o, but I can't find any now. Probably a fluke, or only an issue during a transitional period.

Perhaps you're thinking of http://inbound-archive.pub.build.mozilla.org/ ? That has 4 cycles/~6 months retention.

Pretty sure this was comment #4.