Thalia environments and workflow
The thalia working environment is split into four parts:
- Development - a shared ennvironment for developers to deploy and test new code. Our CI system will build the code from SCM every night and deploy the binary the development server if the build and smoke test are successful.
- Testing - used by QA testers and CAT users. The code on the test server is more stable than that on the development server. During the two week QA process, we will release a new build to QA every three days or whenever important bug(s) are fixed. A release note will be sent to QA along with the new release containing a list of issues resolved in this release.We will give our final release candidate to QA three business days before the actual release date. Currently, we are releasing on Monday night every 4 weeks.
- Production - live service. The production servers have their own sets of passwords to protect the production environment: the tomcat manager password on thalia5 and 8, the alfresco admin user's password and regular user's password. Only root instances are allowed in .k5login files.
We don't have a staging environment at this time. Staging is a stable release containing test data for other services to test against.
Nightly builds and smoke tests run on isda-build1.mit.edu .
We may put files on isda-build1.mit.edu/~isdasnap for AMIT to deploy during release.
|
Development |
Testing |
Production |
|---|---|---|---|
hostname |
thalia-dev.mit.edu |
thalia-test.mit.edu |
thalia.mit.edu |
IME (back end) and help files |
cms-dev-th1.mit.edu |
isda-thalia2, isda-thalia11 |
isda-thalia5, isda-thalia8 |
Alfresco |
cms-dev-th2.mit.edu |
isda-thalia9 |
isda-thalia6 |
MySQL |
cms-dev-th3.mit.edu |
isda-thalia13 (thaliaunicode) |
isda-thalia7 |
value for repository.location in |
|||
|
|
|
|
|
|
|
|