If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

AMO talos uses buildbot-custom and http://build.mozilla.org/talos to find talos.zip

RESOLVED FIXED

Status

Testing
Talos
RESOLVED FIXED
6 years ago
5 years ago

People

(Reporter: jmaher, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
with the latest changes to buildbot-config where we can deploy a talos.zip dynamically based on a .json file in the source repository, we need to figure out which method is needed for AMO.

Either:
1) we stick with the 100% hard-coded http://build.mozilla.org/talos and live with it
2) adopt a similar approach where we pull from a repository, in this case probably m-c.

Comment 1

6 years ago
What config does the AMO setup use?

If we stick with 1) we could at some point forget that zips/talos.zip is used and break the AMO setup without knowing.

Against which branches do they test?
(Reporter)

Comment 2

6 years ago
http://releases.mozilla.org/pub/mozilla.org/firefox/releases/latest*:
3.6
9.0

right now we just do these two branches.  I have a version of buildbot-config an buildbotcustom on this buildbot machine.

Comment 3

6 years ago
ah OK cool. I just realized this is a Testing/Talos bug.
Let me know if you need any help from me.
(Reporter)

Comment 4

6 years ago
yeah, this is a placeholder more than anything.  I haven't updated the buildbot stuff, so I will need to resolve this before updating buildbot code on the AMO server.
(Reporter)

Comment 5

5 years ago
we are not using talos to test performance on AMO.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.