Subversion Repositories DevTools

Rev

Rev 243 | Go to most recent revision | Show entire file | Ignore whitespace | Details | Blame | Last modification | View Log | RSS feed

Rev 243 Rev 5730
Line 35... Line 35...
35 
 
 35 
 
36 
 
 36 
 
37 
JATS Requirements
 37 
JATS Requirements
38 
-----------------
 38 
-----------------
39 
 
 39 
 
40 
1) Perl 5.6.1 or better
 40 
1) Perl no later than 5.8.8
41 
2) Compilers and tools as required by the targets being built
 41 
2) Compilers and tools as required by the targets being built
42 
 
 42 
 
43 
========================================================================
 43 
========================================================================
44 
 
 44 
 
45 
Host-specific Installation Operation
 45 
Host-specific Installation Operation
Line 62... Line 62...
62 
1) Create a New automated version in Release Manager
 62 
1) Create a New automated version in Release Manager
63 
   Use: HOME > TECHNOLOGY GROUP > Build Environment TOOLS
 63 
   Use: HOME > TECHNOLOGY GROUP > Build Environment TOOLS
64 
   The package is 'core_devl'
 64 
   The package is 'core_devl'
65 
 
 65 
 
66 
2) Make changes to the JATS files
 66 
2) Make changes to the JATS files
67 
   Clearcase config Spec:
 - 
 
68 
        element /MASS_Dev_Infra/... .../mass_dev/LATEST
 - 
 
69 
        element /MASS_Dev_Infra/... /main/LATEST
 - 
 
70 
        load    /MASS_Dev_Infra/core_devl
 - 
 
71 
 
 67 
 
72 
3) Update the ChangeLog.txt file
 68 
3) Update the ChangeLog.txt file
73 
   Leave the 'VERSION' as current.
 69 
   Update the Version
74 
   Update the Release Date.
 70 
   Update the Release Date.
- 
 
 71 
   Describe changes
75 
 
 72 
 
76 
4) Label ALL files in the core_devl view with the CORE_DEVL.XXXX.CR.WIP label
 73 
4) Label ALL files in the core_devl view with the CORE_DEVL.XXXX.CR.WIP label
- 
 
 74 
   or the label provided by Release Manager.
77 
 
 75 
 
78 
5) Use Release Manager to Release and build the package
 76 
5) Use Release Manager to Release and build the package
79 
   The Build Demons should build and install the package
 77 
   The Build Demons should build and install the package
- 
 
 78 
   The PostInstall processing will be run
80 
 
 79 
 
81 
6) On "auperaunx26", locate the released package and run the PostInstall script.
 80 
6) On "auperaarc01", locate the released package in core_devl
82 
        cd core_devl/XX.XX.XX.cr
 - 
 
83 
       ./PostInstall.sh
 - 
 
84 
 
 - 
 
85 
7)Update the softlink to the latest version of JATS
 81 
   Create a symlink from the new version to 'jats_new'
86 
   On "auperaunx26", in the directory /devl/dpkg_archive/core_devl
 - 
 
87 
 
 - 
 
88 
        rm jats2_current
 - 
 
89 
        ln -s dpkg_archive/core_devl/XX.XX.XX.cr jats2_current
 - 
 
90 
 
 - 
 
91 
8) Email the last release note entry to all
 - 
 
92 
 
 - 
 
93 
Creating the JATS package for Release (Manual Release)
 - 
 
94 
------------------------------------------------------
 - 
 
95 
 
 - 
 
96 
1) Make changes to the JATS files
 - 
 
97 
   Clearcase config Spec:
 - 
 
98 
        element /MASS_Dev_Infra/... .../mass_dev/LATEST
 - 
 
99 
        element /MASS_Dev_Infra/... /main/LATEST
 - 
 
100 
        load    /MASS_Dev_Infra/core_devl
 82 
   ie: sudo ln -s 3.10.3000.cr jats2_new
101 
 
 - 
 
102 
2) Update the ChangeLog.txt file
 - 
 
103 
 
 - 
 
104 
3) Label ALL files in the core_devl view with the JATS_XX.XX.XX.cr label
 - 
 
105 
 
 - 
 
106 
4) Use the jats command:
 - 
 
107 
        jats release JATS_XX.XX.XX.cr
 - 
 
108 
   to release the package.
 - 
 
109 
 
 - 
 
110 
5) On "auperaunx26", locate the released package and run the PostInstall script.
 - 
 
111 
        cd core_devl/XX.XX.XX.cr
 - 
 
112 
       ./PostInstall.sh
 - 
 
113 
 
 - 
 
114 
6)Update the softlink to the latest version of JATS
 - 
 
115 
   On "auperaunx26", in the directory /devl/dpkg_archive/core_devl
 - 
 
116 
 
 - 
 
117 
        rm jats2_current
 - 
 
118 
        ln -s dpkg_archive/core_devl/XX.XX.XX.cr jats2_current
 83 
   At 3:00Am Perth Time a cronjob will update jats2_current from jats2_new
119 
 
 - 
 
120 
7) Maintain the Release Manager Entry
 - 
 
121
- 
 
122 
8) Email the last release note entry to all
 - 
 
123 
 
 84 
 
- 
 
 85 
7) Inform users via the Google++ group called: JATS Build System
124 
 
 86 
 
125 
================================================================================
 87 
================================================================================
126 
================================================================================
 88 
================================================================================
127 
Notes on directory layout
 89 
Notes on directory layout
128 
 
 90 
 
129 
The current directory structure is given by the picture below:
 91 
The current directory structure is given by the picture below:
130 
 
 92 
 
131 
    /MASS_Dev_Infra/core_devl/:
 93 
    /.../core_devl/:
132 
      |-BIN.linux_i386/:
 94 
      |-BIN.linux_i386/:
133 
      |-BIN.solaris10_sparc32/:
 95 
      |-BIN.solaris10_sparc32/:
134 
      |-BIN.solaris10_x86/:
 96 
      |-BIN.solaris10_x86/:
135 
      |-BIN.sparc/:
 97 
      |-BIN.sparc/:
136 
      |-BIN.win32/:
 98 
      |-BIN.win32/:
Line 149... Line 111...
149 
      |   |   |-DeployUtils/:
 111 
      |   |   |-DeployUtils/:
150 
      |   |-LOCAL/:
 112 
      |   |-LOCAL/:
151 
      |-UTILS/:
 113 
      |-UTILS/:
152 
 
 114 
 
153 
Details:
 115 
Details:
154 
/MASS_Dev_Infra/core_devl
 116 
/.../core_devl
155 
    The root of the core_devl view in the ClearCase VOB
 117 
    The root of the core_devl view in the ClearCase VOB
156 
    The only files in the directory should be readme's and the build.pl file
 118 
    The only files in the directory should be readme's and the build.pl file
157 
 
 119 
 
158 
BIN.linux_i386
 120 
BIN.linux_i386
159 
BIN.solaris10_sparc32
 121 
BIN.solaris10_sparc32