1246975 - Configure a staging deployment system

Status: RESOLVED WONTFIX

(developer.mozilla.org Graveyard :: BrowserCompat, defect)

Description

[John Whitlock [:jwhitlock]]

What problem would this feature solve?
======================================
BrowserCompat is currently hosted on Heroku, and deployed when the master branch is updated and TravisCI runs "green", which includes unit and integration tests.

A staging deployment is required for additional integration tests, and to test configuration changes before they are enabled in production.

Who has this problem?
=====================
Staff contributors to MDN

How do you know that the users identified above have this problem?
==================================================================
MDN uses a staging / production system, and many configuration issues are discovered in staging.

How are the users identified above solving this problem now?
============================================================
BC is not yet in production usage. Errors for beta users is not a blocking issue.

Do you have any suggestions for solving the problem? Please explain in detail.
==============================================================================
Jenkins appears to be the Mozilla standard for testing and deployment. One or more instances will be to be provisioned (one for all components, or one for the API, one for the C&M interface, etc.).

One staging configuration [1] is:

- Deployment server (admin.browsercompat.org)
- QA server (qa.browsercompat.org)
- C&M server (www.stage.browsercompat.org)
- API server (api.stage.browsercompat.org)
- Importer (importer.stage.browsercompat.org)
- Table renderer (integrate.stage.browsercompat.org)
- C&M asset CDN (www.stage.cdn.browsercompat.org)
- API asset CDN (api.stage.cdn.browsercompat.org)

Backend services (databases, web workers, task workers, test robots) will also be needed for a full environment. SSL certs will also be required.

In general, the components do not need to be synchronized (for example, an API deployment does not mean the C&M server needs to also be deployed, and vice-versa).

[1] https://wiki.mozilla.org/MDN/Development/CompatibilityTables/Infrastructure#Production_Services

Is there anything else we should know?
======================================

Comment 1

[John Whitlock [:jwhitlock]]

The BrowserCompat project is canceled.  See https://github.com/mdn/browsercompat for current effort. Bulk status change includes the random word TEMPOTHRONE.