Environments SVN etc
From UG
(Difference between revisions)
(→DR/KPI) |
(→Trunk(DQ) and Projects) |
||
| Line 5: | Line 5: | ||
Please keep it updated! | Please keep it updated! | ||
| - | == | + | == Environments and location of related code == |
| - | === | + | === Production === |
| - | * | + | * prod: |
| - | * | + | * staging: |
| - | * SVN: | + | * SVN: |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
=== DQ === | === DQ === | ||
| Line 24: | Line 19: | ||
* staging: | * staging: | ||
* SVN: '''/trunk''' Work in progress | * SVN: '''/trunk''' Work in progress | ||
| + | |||
| + | === GM Split === | ||
| + | * dev: | ||
| + | * UAT: | ||
| + | * SVN: '''/tags/2.24.0''' | ||
=== DR/KPI === | === DR/KPI === | ||
| Line 30: | Line 30: | ||
* UAT: | * UAT: | ||
* SVN: /branches/DR_KPI | * SVN: /branches/DR_KPI | ||
| + | |||
| + | === I Portal === | ||
| + | |||
| + | * dev: dev3-kuchma.jaguarfreight.com | ||
| + | * UAT: same | ||
| + | * SVN: ??? | ||
| + | |||
| + | === POEM === | ||
| + | |||
| + | * dev: | ||
| + | * UAT: | ||
| + | * SVN: | ||
== Misc == | == Misc == | ||
Revision as of 18:50, 27 May 2012
Contents |
About
This wiki is to log what SVN tag/branch is associated with what project/environment.
Please keep it updated!
Environments and location of related code
Production
- prod:
- staging:
- SVN:
DQ
- dev:
- UAT:
- staging:
- SVN: /trunk Work in progress
GM Split
- dev:
- UAT:
- SVN: /tags/2.24.0
DR/KPI
- dev:
- UAT:
- SVN: /branches/DR_KPI
I Portal
- dev: dev3-kuchma.jaguarfreight.com
- UAT: same
- SVN: ???
POEM
- dev:
- UAT:
- SVN:
Misc
Production Releases
- 27/03/2012 /tags/2.23.4
Emergency Release Process
- field
- before task is forwarded to coding (ph is set to Dev) field
- Staging/System Integration QA
- Dev. Manager (KU/Sa) with Release Manager (Roma) must analyze what type of staging (integration testing) is required for particular Emerg. Release, estimate and request appropriate number of days / hours
- only affected components must be tested
Appendix: Definitions, etc.
The trunk is the main line of development in a SVN repository.
A branch is a side-line of development created to make larger, experimental or disrupting work without annoying users of the trunk version. Also, branches can be used to create development lines for multiple versions of the same product, like having a place to backport bugfixes into a stable release.
Finally, tags are markers to highlight notable revisions in the history of the repository, usually things like "this was released as 1.0".
