Confirmed users
176
edits
Apps/QA/Test Infrastructure: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 81: | Line 81: | ||
myapps-staging.apps.mozilla.com | myapps-staging.apps.mozilla.com | ||
This is a where the dashboard will be hosted. Idea is to be able to test dashboard changes before they go live. | This is a where the dashboard will be hosted. Idea is to be able to test dashboard changes before they go live. | ||
== Server Rearrangement == | |||
Some thoughts from Ian: | |||
I think we can move everything to a single server (we'll call it myapps-staging): the HTML shim, the dashboard, the test appdir, and we should be able to generate an XPI there as well, and in addition future sync deployments. | |||
If we can automate this well, then we can potentially base it all on a manifest of repositories. A manifest might look like: | |||
OPENWEBAPPS=https://github.com/mozilla/openwebapps.git | |||
OPENWEBAPPS_BRANCH=update-api | |||
OPENWEBAPPS_REV=99a844f | |||
BROWSERID_SITE=https://diresworb.org | |||
And do the same thing for each component (since we have multiple repos). If we can build that on a brand new VM (maybe just an externally hosted cloud VM) we can really let people create their own manifests to test other combinations. | |||