set up a new development master for tegra testing

RESOLVED FIXED

Status

Infrastructure & Operations
Buildduty
RESOLVED FIXED
6 years ago
16 days ago

People

(Reporter: kmoir, Assigned: kmoir)

Tracking

Details

(Assignee)

Description

6 years ago
and document the process too :-)
(Assignee)

Updated

6 years ago
Assignee: nobody → kmoir
(Assignee)

Comment 1

6 years ago
I've temporarily moved the tegras attached to staging foopy05 to the new staging tegra master http://dev-master01.build.scl1.mozilla.com:8036 and am running tests, but so far my sendchanges aren't triggering anything.  Will look at this again a bit later.
(Assignee)

Comment 2

6 years ago
All the tegras from foopies 05 and 06 are moved to the new staging master.  The sendchange script is running builds within a screen session running as my userid.  The master is http://dev-master01.build.scl1.mozilla.com:8036 and is stored in /builds/buildbot/kmoir/test2.  Callek, you should be able to ssh as me to the machine and attach to my screen session.  Let me know if there are any issues with this instance, if not we can stop the old one and close this bug.

I updated the documentation on the wiki too, most of the steps were already there.
(In reply to Kim Moir [:kmoir] from comment #2)
> Callek, you should be able
> to ssh as me to the machine and attach to my screen session.  Let me know if
> there are any issues with this instance, if not we can stop the old one and
> close this bug.

Ok, so this lgtm. However coop said in passing that he might want a "proper" staging setup, outside of dev-master01 for the tegra/mobile master[s] at this point, rather than just having this bounce around our user accounts. I'd like his final-signoff.

But even without it, I think we're in a good shape that we can turn off (and delete history from) bear's test master.
(Assignee)

Comment 4

6 years ago
I talked to coop today and he said that for now it would be fine for it to run under my userid on dev master and we could revisit running it under its VM later on. For now, I've stopped bear's dev master and the script running the sendchanges.  We can look at the files from the old instance in a few weeks and decide if there are any files that need to be saved before deleting it.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.