Environments SVN etc

From UG

(Difference between revisions)
Jump to: navigation, search
(Environments and location of related code)
(Environments and location of related code)
 
(3 intermediate revisions not shown)
Line 31: Line 31:
* dev: dev3-kuchma.jaguarfreight.com
* dev: dev3-kuchma.jaguarfreight.com
* UAT: same
* UAT: same
-
* SVN: ???
+
* SVN: /branches/InternationalPortal
=== DR/KPI ===
=== DR/KPI ===
Line 41: Line 41:
=== POEM ===
=== POEM ===
-
* dev: dev3-kuchma.jaguarfreight.com
+
* dev: TBD
* UAT: same
* UAT: same
* SVN: /branches/POEM
* SVN: /branches/POEM
 +
 +
=== ASN 20 ===
 +
 +
* dev: dev3-kuchma.jaguarfreight.com
 +
* UAT: same
 +
* SVN: /branches/asn2.0
== Misc ==
== Misc ==
Line 77: Line 83:
* http://svn.apache.org/repos/asf/subversion/trunk/doc/user/svn-best-practices.html
* http://svn.apache.org/repos/asf/subversion/trunk/doc/user/svn-best-practices.html
 +
 +
* http://nvie.com/posts/a-successful-git-branching-model/

Current revision as of 16:15, 5 September 2012


Contents

[edit] Environments and location of related code

[edit] Production

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

[edit] Staging Of Production

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

[edit] DQ

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

[edit] GM Split

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

[edit] I Portal

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

[edit] DR/KPI

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

[edit] POEM

  • dev: TBD
  • UAT: same
  • SVN: /branches/POEM

[edit] ASN 20

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

[edit] Misc

[edit] History of Production Releases

  • 27/03/2012 /tags/2.23.4

[edit] 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

[edit] 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".

[edit] References

Personal tools