add-on perf tests shouldn't hit external servers

RESOLVED INVALID

Status

Release Engineering
General
P3
normal
RESOLVED INVALID
6 years ago
4 years ago

People

(Reporter: bhearsum, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [automation][ftp])

(Reporter)

Description

6 years ago
We're trying to turn off external access to the network for test slaves. Addon tests are one of the last things still requiring outside access. We need to:
* Change this base_url to stage.mozilla.org or ftp.mozilla.org in TalosFactory: http://hg.mozilla.org/build/buildbotcustom/file/tip/process/factory.py#l7420
* Change the list of addons (http://hg.mozilla.org/build/puppet-manifests/file/958f195d38a9/modules/addon-sendchanges/files/addons.txt) to use different style paths. From /en-US/firefox/downloads/latest/722 to /pub/mozilla.org/addons/722/noscript-2.1.5-fn+sm+fx.xpi. Not sure how to cope with version changes yet....

Updated

6 years ago
Priority: -- → P3
Whiteboard: [automation][ftp]

Comment 1

6 years ago
I thought that the weekly talos addon test was just a stop gap until we got the on-demand addon talos testing working, which I have been told is currently working.  So, why are we still doing the weekly test at all?  Is that still valid?  All for it if it is, just want to be sure we're not doing work for something that we should just turn off.
They are not working yet.  Tracker is bug 690595 but there is stuff on the graph server side that is currently being done before the AMO side.  jmaher is working on it.

Comment 3

6 years ago
If you want to keep the build net secure, you shouldn't be running code from AMO in it at all.
(Reporter)

Comment 4

5 years ago
These tests died in bug 778998
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WONTFIX

Updated

5 years ago
Resolution: WONTFIX → INVALID
(Assignee)

Updated

4 years ago
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.