Upgrade SUTAgent to 1.14 on tegras in production

RESOLVED FIXED

Status

Testing
General
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: Callek, Assigned: Callek)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

5 years ago
We need to update SUTAgent to v1.14 on the tegras in production, the apk has already been staged, and things look good in staging
(Assignee)

Comment 1

5 years ago
NOW the last of the tegras are coming back up, with the directive to install the new SUTAgent. if this fails in any way on a device we'll simply [automatically] choose to not start buildbot for that device.

http://hg.mozilla.org/build/tools/rev/f25f378dd283 was the landing for telling it to use 1.14
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
(Assignee)

Comment 2

5 years ago
FYI, since this is the bug I know of, this was broken since its landing:

[root@relengweb1.dmz.scl3 mobile]# ls -l
total 636
drwxr-s--- 2 armenzg 101   4096 May  8  2012 delete
-rwxr-xr-x 1 armenzg 101  61051 Mar 12  2012 sutAgentAndroid.1.07.apk
-rw-r--r-- 1 armenzg 101  61747 May  8  2012 sutAgentAndroid.1.08.apk
-rw-r--r-- 1 armenzg 101  62132 Jun 23 14:03 sutAgentAndroid.1.09.apk
-rw-r--r-- 1 armenzg 101  63395 Jul 27 09:31 sutAgentAndroid.1.11.apk
-rw-r--r-- 1 armenzg 101  63714 Aug 23 14:46 sutAgentAndroid.1.12.apk
-rw-r--r-- 1 root    101  64170 Sep  7 13:59 sutAgentAndroid.1.13.apk
-rw-r--r-- 1 root    101 227672 Oct 18 10:30 SUTAgentAndroid.1.14.apk
[root@relengweb1.dmz.scl3 mobile]# mv SUTAgentAndroid.1.14.apk sutAgentAndroid.1.14.apk

I just had to do that, case matters :(

Updated

5 years ago
Component: Infrastructure → General
You need to log in before you can comment on or make changes to this bug.