1217486 - unable to retrigger jobs on mozilla-beta, unable to push those revisions to try

Status: RESOLVED WORKSFORME

(Release Engineering :: General, defect)

Description

[Joel Maher ( :jmaher ) (UTC -8)]

I did 4 pushes to try:
https://treeherder.mozilla.org/#/jobs?repo=try&author=[e-mail]&fromchange=48d248f92367

1 of them actually worked, the rest failed miserably.  The last 2 with all failures were the last pushes to firefox 38 and firefox 39.  Sadly there seems to be missing config files or something, I thought all our mozharness bits were in tree!

I tried to retrigger an existing job from THIS WEEK, and I get infra failures where it is unable to download the url:
https://treeherder.mozilla.org/#/jobs?repo=mozilla-beta&revision=a01cadb2a94d

I believe that is related to the ftp->s3 stuff, we still need the data.

The problem we have is we want to compare performance back to a few versions and we are unable to do that as treeherder doesn't have data nor do we keep builds around past 90 days.  And it appears we cannot generate our own builds from a previous time.

Comment 1

[Nick Thomas [:nthomas] (UTC+12)]

Sorry, I thought I'd replied to this already.

(In reply to Joel Maher (:jmaher) from comment #0)
> I did 4 pushes to try:
> https://treeherder.mozilla.org/#/jobs?repo=try&author=jmaher@mozilla.
> com&fromchange=48d248f92367
> 
> 1 of them actually worked, the rest failed miserably.  The last 2 with all
> failures were the last pushes to firefox 38 and firefox 39.  Sadly there
> seems to be missing config files or something, I thought all our mozharness
> bits were in tree!

Those must have been before I landed all the config change on mozilla-beta and higher. Have you had better results more recently ?

> I tried to retrigger an existing job from THIS WEEK, and I get infra
> failures where it is unable to download the url:
> https://treeherder.mozilla.org/#/jobs?repo=mozilla-beta&revision=a01cadb2a94d

All the older files should have been synced in as of a week and and half ago. There was a slight underestimation of how long it would take to sync data across.

> The problem we have is we want to compare performance back to a few versions
> and we are unable to do that as treeherder doesn't have data nor do we keep
> builds around past 90 days.  And it appears we cannot generate our own
> builds from a previous time.

This is always going to be tricky on try because it's only really supported to compile mozilla-central. Can you make any progress with just the installers, or the files still in http://archive.mozilla.org/pub/mozilla.org/firefox/candidates/ ?

Perhaps you can run talos jobs on try like this:
* push to try to get a revision in the system, but abandon the builds immediately (or build something unrelated but cheap like android)
* then use mozci to trigger talos tests and pass a list of files from either the candidates url above, or release

Alternatively find the closest revision on the default branch of beta/wherever and redo the CI builds using self-serve ? The buildbot DB goes back 6 months, and buildapi should let you redo builds that far back.

Comment 2

[Joel Maher ( :jmaher ) (UTC -8)]

retriggers on beta work fine now.  This might work out by using the candidates.  I will have to look into how to use the candidate urls and play with that a bit- probably a worthwhile effort.