Closed Bug 943873 Opened 11 years ago Closed 10 years ago

Autophone - support inbound archive

Categories

(Testing Graveyard :: Autophone, defect)

x86_64
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bc, Assigned: bc)

References

Details

Attachments

(1 file)

When triaging Autophone results in the far far away it would be good to allow us to test builds from the inbound archive: http://inbound-archive.pub.build.mozilla.org/pub/mozilla.org/mobile/tinderbox-builds/
Tested with:

python trigger_runs.py --build-location=inboundarchive --repo=mozilla-inbound --loglevel=DEBUG 2013-08-20 2013-08-31

Warning: takes a long time to deal with all 7500 entries.
Attachment #8341217 - Flags: review?(mcote)
Comment on attachment 8341217 [details] [diff] [review]
bug-943873-inbound-archive.patch

Review of attachment 8341217 [details] [diff] [review]:
-----------------------------------------------------------------

::: trigger_runs.py
@@ +130,4 @@
>      parser.add_option('-b', '--build-location', action='store', type='string',
>                        dest='build_location', default='nightly',
>                        help='build location to search for builds, defaults to nightly;'
> +                      ' can be "tinderbox" or "inboundarchive" for both m-c and m-i')

Not directly related to this patch, but thinking we should rename tinderbox at some point, since, well, we don't use tinderbox anymore.  Maybe "trunk"?  I'm not sure what the current nomenclature is.
Attachment #8341217 - Flags: review?(mcote) → review+
Yeah, I think the generalization of the "get stuff from build directories" is an opportunity to get a consistent nomenclature determined.

https://github.com/mozilla/autophone/commit/06bb072816f5ca855051dd351d0b1f583a5cd657
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.