summaryrefslogtreecommitdiff
path: root/ci-arch.mdwn
diff options
context:
space:
mode:
authorLars Wirzenius <lwirzenius@wikimedia.org>2019-05-02 19:59:25 +0300
committerLars Wirzenius <lwirzenius@wikimedia.org>2019-05-02 19:59:25 +0300
commit961b1b512c7bacc733212125eab2b7c021e1bece (patch)
tree462e9b8b2dd0939a3da447325c82df47cd76b9ac /ci-arch.mdwn
parent6b3f41d5adba2200691678b61922af9dbf76b584 (diff)
downloadwmf-ci-arch-961b1b512c7bacc733212125eab2b7c021e1bece.tar.gz
Change: clarify DEPLOYWHEREVER
Diffstat (limited to 'ci-arch.mdwn')
-rw-r--r--ci-arch.mdwn8
1 files changed, 6 insertions, 2 deletions
diff --git a/ci-arch.mdwn b/ci-arch.mdwn
index 9277710..5b10041 100644
--- a/ci-arch.mdwn
+++ b/ci-arch.mdwn
@@ -282,8 +282,12 @@ TITLE: Future WMF CI architecture
* **(POSTMERGEBISECT)** Would be nice to post-merge git-bisect to find
patch that caused a particular problem with a Selenium test.
-* **(DEPLOYWHEREVER)** Would be nice to have a mechanism for deployment to
- staging, production, pypi, packagist, toollabs.
+* **(DEPLOYWHEREVER)** Would be nice to have a mechanism for
+ deployment to staging, production, pypi, packagist, toollabs. We
+ could do with a way to deploy to any of several possible
+ environments, for various use cases, such as bug repoduction, manual
+ exploratory testing, capacity testing, and production. FIXME: what
+ do pypi and packagist do in the list?
* **(MATRIXBUILDS)** Would be nice to have efficient matrix builds.