Subversion Repositories DevTools

Rev

Go to most recent revision | Details | Last modification | View Log | RSS feed

Rev Author Line No. Line
315 dpurdie 1
#-------------------------------------------------------------------------------
2
#   Documentation
3
#
4
 
5
=pod
6
 
7
=head1 NAME
8
 
9
JATS Environment Variables
10
 
11
=head1 SYNOPSIS
12
 
13
JATS makes use of a number of Environment Variables (EnvVars) to provide
14
configuration information.
15
 
16
There are two classes of EnvVars used by JATS. These are:
17
 
18
=over
19
 
20
=item 1 JATS Configuration
21
 
22
These EnvVars have a GBE_ prefix. These are detailed in this document.
23
 
24
=item 2 Toolset location
25
 
26
Some of the build tools used by JATS use EnvVars to specify the location
27
of the installed tool. 
28
 
29
Ideally tools should be installed in their default location and JATS should be
30
preconfigured to use this default location. Configuration allows for exceptions.
31
 
32
=back
33
 
34
=head2  Environment variables
35
 
36
Environment variables that specify a path may be set to '-', or 'none' in order
37
to force an undefined path.
38
 
39
=over 8
40
 
41
=item GBE_MACHTYPE
42
 
43
This specifies the machine that the script is running on. This is fixed within
44
the startup script.
45
 
46
=item GBE_HOSTMACH (internally set)
47
 
48
This is a copy of GBE_MACHTYPE.
49
Unlike GBE_MACHTYPE, this copy is not modified by makefiles.
50
 
51
=item GBE_HOSTNAME (internally)
52
 
53
This EnvVar is the name of the current host. It is available to be used within
54
scripts that need to stamp build files.
55
 
56
=item GBE_PERL
57
 
58
This specifies the full path the to B<ActiveState> perl binary.
59
 
60
=item GBE_CORE
61
 
62
This specifies the path the to B<JATS> installation.
63
 
64
=item GBE_CACHE_JATS
65
 
66
When set to a non zero value will force JATS to transfer a working copy to the
67
local dpkg_archive. This will speed up the build process because the utilities
68
will be run from a local drive; not a network drive.
69
 
70
This will only operate if JATS is run from dpkg_archive.
71
 
72
=item GBE_DPKG_STORE (optional)
73
 
74
This is the global read-only archive store. It will only be used to source
75
packages after all other archive stores have been examined. The GBE_DPKG_STORE
76
is intended to provide a read-only or remote repository within a global
77
environment.
78
 
79
=item GBE_DPKG
80
 
81
This is the official archive. Some tools will publish packages directly to this
82
archive.
83
 
84
This item is mandatory and must address a valid directory.
85
 
86
=item GBE_DPKG_CACHE (optional)
87
 
88
This the path to a local package archive cache. This is used to speed access to
89
main repository. The cache should be on the users local machine and not a network
90
drive.
91
 
92
=item GBE_DPKG_LOCAL (optional)
93
 
94
This the path to a group wide local package archive. This may be used to store
95
non-official packages that are under test or development.
96
 
343 dpurdie 97
Not recommended. Use is being deprecated.
315 dpurdie 98
 
343 dpurdie 99
=item GBE_DPKG_SBOX (internal)
100
 
101
This the path to a sandbox specific package archive. This will be used to store
315 dpurdie 102
non-official packages that are under test or development within the current sandbox.
103
 
104
The archive is located by searching from the current directory to the root of
343 dpurdie 105
the file system for a directory called 'sandbox_dpkg_archive'.
315 dpurdie 106
 
107
It is intended that a group of packages that are being developed in the same
108
sandbox will share the same sandbox_dpkg_archive.
109
 
110
Jats will ignore the version number when dealing with packages in GBE_DPKG_SBOX.
111
This is done to simplify the publishing and consuming of packages in the sandbox.
112
 
113
This should not be set by a user. It will be calculated by JATS and passed to
114
JATS tools and utilities.
115
 
343 dpurdie 116
=item GBE_SANDBOX (internal)
315 dpurdie 117
 
118
This the path to a sandbox base directory. It is intended that a group of
119
packages that are being developed in the same sandbox will share the same
120
sandbox_dpkg_archive.
121
 
122
This should not be set by a user. It will be calculated by JATS and passed to
123
JATS tools and utilities.
124
 
125
=item GBE_DPLY (optional)
126
 
127
This the path to the deployment archive.
128
This archive will be used when publishing special deployment package. This is
129
not the norm.
130
 
131
This variable may be set on a per-project basis.
132
 
133
=item GBE_PLATFORM (deprecated)
134
 
135
This specifies the names of platforms that will be built and made. This should
136
be empty. Use B<GBE_BUILDFILTER> to provide better control.
137
 
138
=item GBE_BUILDFILTER (desirable)
139
 
140
This is a filter string that specifies which platforms to create makefiles
141
for. This variable is used to prevent JATS from creating Solaris and Linux
142
targets on a Windows machine and visa-versa.
143
 
144
=item GBE_JATS_VERSION (optional)
145
 
146
Specifies the version of JATS that the user will use. This is the same as
147
specifying the -version=xx.xx.xx option on the command line, but because it is
148
in the environment the required version will be used by all invocations of JATS.
149
 
150
=item GBE_ABT (optional)
151
 
152
Used by the Auto Build Tool to indicate that the build is being performed by the
153
ABT. When set the build environment will be modified to suite the ABT. Some
154
operations may be relaxed.
155
 
156
Currently set to 1 to set it.
157
 
158
=item GBE_VIEWBASE (optional)
159
 
343 dpurdie 160
Used by the 'release' utilities to provide a user configurable base directory for
161
the creation of static views. The default location is:
315 dpurdie 162
 
343 dpurdie 163
=over 8
164
 
165
=item WINDOWS - c:\clearcase
166
 
167
=item Unix - jats_cbuilder and is relative to the users HOME directory.
168
 
169
=back
170
 
315 dpurdie 171
=item GBE_RM_LOCATION (optional)
172
 
173
Used by tools that interface to Release Manager: primarily the (ABT) Auto Build Tools.
174
Specifies the location of the Release Manager Database. This is a database url
175
of the form jdbc:subprotocol:subname as used by java.sql.DriverManager.getConnection()
176
 
177
C<Example: jdbc:oracle:thin:@auperaora03:1521:RELEASEM>
178
 
179
=item GBE_RM_USERNAME (optional)
180
 
181
Used by tools that interface to Release Manager: primarily the (ABT) Auto Build Tools.
182
Specifies a USERNAME with access to the Release Manager Database.
183
 
184
=item GBE_RM_PASSWORD (optional)
185
 
186
Used by tools that interface to Release Manager: primarily the (ABT) Auto Build Tools.
187
Specifies a PASSWORD to be used in conjunction with GBE_RM_USERNAME to access
188
the Release Manager Database.
189
 
190
=item GBE_RM_URL (optional)
191
 
192
Used by tools that interface to Release Manager: primarily the (ABT) Auto Build Tools.
193
Specifies the base URL of RElease Manager
194
 
195
=item GBE_DM_LOCATION (optional)
196
 
197
Similar to GBE_RM_LOCATION, but is used to access the Deployment Manager Database.
198
If GBE_DM_LOCATION is not provided, then GBE_RM_LOCATION will be used.
199
 
200
=item GBE_DM_USERNAME (optional)
201
 
202
Similar to GBE_RM_USERNAME, but is used to access the Deployment Manager Database.
203
 
204
=item GBE_DM_PASSWORD (optional)
205
 
206
Similar to GBE_RM_PASSWORD, but is used to access the Deployment Manager Database.
207
 
208
=item GBE_DM_URL (optional)
209
 
210
Similar to GBE_DM_URL, but is used to access the Deployment Manager Database.
211
 
341 dpurdie 212
=item GBE_SVN_URL (Required for Subversion support)
315 dpurdie 213
 
341 dpurdie 214
Specifies the URL of the Subversion repository to be used by the Subversion
215
oriented JATS commands. The URL should contain the protocol, the repository
216
host and the path to the root of the repository, but not the name of the
217
repository. ie: C<svn://auperaws996vm21>
315 dpurdie 218
 
219
=item GBE_SVN_PATH (optional)
220
 
221
If provided this will be used to locate the 'svn' utility used by the SubVersion
222
support functions. If not provided, then the utilities assume that 'svn' is in the
341 dpurdie 223
users PATH. 
315 dpurdie 224
 
341 dpurdie 225
Providing the path will prevent JATS from searching for the utility.
226
 
315 dpurdie 227
=item GBE_SVN_USERNAME (optional)
228
 
229
Subversion repository credentials. If provided it will be used, otherwise the
230
native svn credential mechanism will be used.
231
 
232
=item GBE_SVN_PASSWORD (optional)
233
 
234
Subversion repository credentials. If provided it will be used, otherwise the
235
native svn credential mechanism will be used.
236
 
237
=item GBE_MAKE_TYPE (internal)
238
 
239
This EnvVar is set when a Makefile is being processed by 'make'. The value
240
indicates the type of the build. It will be either P(Production), D(debug)
241
or C(Common).
242
 
243
=item GBE_MAKE_TARGET (internal)
244
 
245
This EnvVar is set when a Makefile is being processed by 'make'. The value
246
is set current target platform name.
247
 
248
=item GBE_MAKE_CFG (internal)
249
 
250
This EnvVar is set when a Makefile is being processed by 'make'. The value
251
is set to the path of the parsed makefile.pl data gathered when the makefile
252
was created.
253
 
254
=item GBE_MAKE_CMD (internal)
255
 
256
This EnvVar is set when a Makefile is being processed by 'make'. The value
257
is set current make command being processed.
258
 
259
=item GBE_SCRIPT (internal)
260
 
343 dpurdie 261
This EnvVar contains the path and command line argument to the current JATS
315 dpurdie 262
command.
263
 
264
Its primary purpose is to determine the location of the jats startup script:
265
jats.bat or jats.sh.
266
 
267
=item GBE_UNIX (internal)
268
 
269
This EnvVar will be set to 1 on Unix systems and 0 on Windows Systems. The value
270
is calculated by JATS and cannot be set externally.
271
 
272
=item USER (set if undefined)
273
 
274
This EnvVar will be set to the current JATS user. It may be set externally,
275
but normally this is not required as JATS will determine the user in a
276
platform specific manner.
277
 
278
=back
279
 
280
=head2 Location of EnvVar definitions
281
 
282
The location of the EnvVars used by JATS is dependent on the target machine
283
type.
284
 
285
=head3 Windows 
286
 
287
Under Windows, the best place to specify the JATS EnvVars is in the JATS.BAT
288
file itself. The location of the JATS.BAT file being used is provided by the '
289
jats vars' utility.
290
 
291
=head3 Solaris
292
 
293
Under Solaris, the JATS EnvVars are set in /etc/profile. These can be
294
overridden by users in there own profile, but this is not encouraged as the
295
JATS configuration is normally machine-wide.
296
 
343 dpurdie 297
The jats.sh script, used to start jats may provide default definitions. The
315 dpurdie 298
location of this script is provided by the 'jats vars' utility.
299
 
300
=head3 Linux
301
 
302
Under Linux, the JATS EnvVars are set in  /etc/profile.d/jats.sh. These can be
303
overridden by users in there own profile, but this is not encouraged as the
304
JATS configuration is normally machine-wide.
305
 
343 dpurdie 306
The jats.sh script, used to start jats may provide default definitions. The
315 dpurdie 307
location of this script is provided by the 'jats vars' utility.
308