Environments SVN etc

From UG

Revision as of 16:31, 12 July 2012 by Alex (Talk | contribs)
Jump to: navigation, search


Contents

Environments and location of related code

Production

  • prod: ct.jaguarfreight.com
  • SVN prod:
  • Version: 2.24.2 (as of 6/26/12)

Staging Of Production

  • staging: staging.jaguarfreight.com
  • SVN staging:
  • Version: 2.25.0 (as of 6/26/12)

DQ

  • dev: dev-kuchma.jaguarfreight.com
  • UAT: same
  • SVN: /trunk

GM Split

  • dev: dev.jaguarfreight.com
  • UAT: uat.jaguarfreight.com
  • SVN: /tags/2.24.0

I Portal

  • dev: dev3-kuchma.jaguarfreight.com
  • UAT: same
  • SVN: /branches/InternationalPortal

DR/KPI

  • dev: dev4-kuchma.jaguarfreight.com
  • UAT: same
  • SVN: /branches/DR_KPI

POEM

  • dev: TBD, used dev3-kuchma.jaguarfreight.com
  • UAT: same
  • SVN: /branches/POEM

Misc

History of 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".

References

Personal tools