Thread:Talk:Continuous integration/also deploy from Jenkins to beta cluster?/reply

I like this idea a lot! I thought about adding a check in this Jenkins hook to also check codereview status of the rev that it would update to the "latest reviewed revision" that passes the unit tests. However after the Git migration, if it's watching mediawiki-core/master those only contain reviewed commits anyway, so that such check is no longer necessary. Nice :)

lab's "beta" project (renamed from "deployment-prep") was originally meant to show the next release, not alpha ("master" or "svn trunk"). I don't think that should be running off trunk. However it should be relatively easy to set up another labs' project named "mw-alpha" that would run on the latest stable "master" rev, and "mw-beta" would keep running on the newest release branch (currently REL1_19, and updated to REL1_20 when it is branched, etc.). It makes sense to have both "mw-alpha" and "mw-beta" be updated by a Jenkins hook. Although right now we don't monitor REL1_19 in Jenkins (we should!), previously when we still used phpUnderControl we did monitor the latest release branch.