Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
ci-admin environment is changing from production to legacy
0 views
Skip to first unread message
Tom Prince
Oct 31, 2019, 3:45:03 PM10/31/19
to release-relops, tools-ta...@lists.mozilla.org
tl;dr You will need to pass `--environment legacy` instead of `--environment
production` when running ci-admin.
ci-admin has a required argument `--environment` that, historically, the
only reasonable option has been `production`. In preparation for the
cluster migration on Nov 9, I am about to land a change that renames the
environment to `legacy` to match the name that is being used for the
existing cluster. There is also a `staging` and I am adding a `firefoxci`
environment.
-- Tom
production` when running ci-admin.
ci-admin has a required argument `--environment` that, historically, the
only reasonable option has been `production`. In preparation for the
cluster migration on Nov 9, I am about to land a change that renames the
environment to `legacy` to match the name that is being used for the
existing cluster. There is also a `staging` and I am adding a `firefoxci`
environment.
-- Tom
0 new messages