Send sendchanges for releases to pm01:9009 after switchover to schedulerDB

RESOLVED FIXED

Status

P2
normal
RESOLVED FIXED
8 years ago
5 years ago

People

(Reporter: armenzg, Assigned: armenzg)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

(Assignee)

Description

8 years ago
Created attachment 463182 [details] [diff] [review]
sendchanges to the right place after schedulerDB has been enabled

We are now using schedulderDB for the testing masters and we need to send the correct sendchanges for our releases.

The patch removes sending sendchanges to the testing masters but instead it sends them to the schedulder DB.
I also removed talos-master since it does not exist anymore.
Do we have a schedulerDB for the talos-staging machines?

We will have to remove this once we move releases to use schedulerDB:
> 'production-master.build.mozilla.org:9010'
Attachment #463182 - Flags: review?(catlee)
(Assignee)

Updated

8 years ago
Assignee: nobody → armenzg
Status: NEW → ASSIGNED
Priority: -- → P2
(Assignee)

Comment 1

8 years ago
Created attachment 463574 [details] [diff] [review]
sendchanges to the right place after schedulerDB has been enabled

I am not removing talos-master since there is where the tiger slaves live.

This fix will help for following releases.
Attachment #463574 - Flags: review?(ccooper)
(Assignee)

Updated

8 years ago
Attachment #463182 - Attachment is obsolete: true
Attachment #463182 - Flags: review?(catlee)
(Assignee)

Updated

8 years ago
Summary: Fix our list of talos_masters and unittest_masters for releases → Send sendchanges for releases to pm01:9009 after switchover to schedulerDB
Attachment #463574 - Flags: review?(ccooper) → review+
(Assignee)

Comment 2

8 years ago
Comment on attachment 463574 [details] [diff] [review]
sendchanges to the right place after schedulerDB has been enabled

http://hg.mozilla.org/build/buildbot-configs/rev/d2decc882736

pm reconfigured.
Attachment #463574 - Flags: checked-in+
(Assignee)

Updated

8 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.