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

Let's grant ateam permission to upload new talos zip files

RESOLVED WONTFIX

Status

Release Engineering
General
RESOLVED WONTFIX
3 years ago
5 months ago

People

(Reporter: pmoore, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Currently A-Team (typically :jmaher) needs to make a request to releng to upload a new version of the talos zip file to netapp on relengwebadm:
https://wiki.mozilla.org/ReleaseEngineering/Buildduty/Other_Duties#Talos

See e.g. bug 1002780, bug 1037377 for two I have worked on, I'm sure others have done many more.

This could maybe be done with careful restricted access to this directory, or even something as simple as an rsync from an a-team location to this directory on relengwebadm. The rsync could either be cron'd or triggered e.g. via jenkins or some other web interface, or some other way the ateam prefers.

Comment 1

3 years ago
Thanks Pete! This is greatly appreciated.

Something more beneficial that this would be to have a way to upload to our internal pypi web hosts.

We could remove the need to use talos.zip completely if we fixed mobile talos to behave like desktop.
On desktop we checkout talos rather than download talos.zip:
http://hg.mozilla.org/build/mozharness/file/58debbd1383a/mozharness/mozilla/testing/talos.py#l483
keep in mind for pandas we checkout the root talos code, but for tegras we do not.  When we stop running tests on tegras, this should not be an issue anymore.
I'll raise a separate bug for pypi packages then, and close this one. Thanks guys!
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
Raised bug 1037466 re: comment 1, comment 3.
(Assignee)

Updated

5 months ago
Component: Tools → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.