1249146 - Submit Taskcluster jobs to the stage Treeherder Heroku instance too

Status: RESOLVED WONTFIX

(Taskcluster :: Services, defect)

Description

[Ed Morley [:emorley]]

Treeherder is wanting to migrate to Heroku this quarter. As part of that migration, we need to do performance and correctness testing on a Heroku instance, before switching over for real.

We already have a prototype Heroku instance running that is ingesting the buildbot jobs (via builds-4hr), however it is missing the jobs submitted via the Treeherder API (mainly Taskcluster).

We're about to spin up a proper staging Heroku instance - that will be copied from the current prod Treeherder DB. Once that happens, we'd like to get Taskcluster to submit to both the existing production Treeherder and also this new stage Heroku instance.

a) Which taskcluster repos/configurations would need updating to do this?
b) Any ideas how much extra work it's going to be to get dual submission to two APIs, or is this already supported?

Many thanks :-)

Comment 1

[Greg Arndt [:garndt]]

Currently we do not support submitting to two apis from a single mozilla-taskcluster instance.  However, we do have two mozilla-taskcluster instances (one for prod and one for staging).  We could possibly point the staging version of mozilla-taskcluster to the heroku instance.

Comment 2

[Ed Morley [:emorley]]

Thank you for your reply.
I think the best way forwards will just to be to swap the Treeherder stage DNS over and replace the SCL3 stage with the Heroku one. If we do this, taskcluster won't need to make any changes, so this bug is redundant :-)