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
 
97
=item GBE_DPKG_SBOX (optional)
98
 
99
This the path to a sandbox specific package archive. This may be used to store
100
non-official packages that are under test or development within the current sandbox.
101
 
102
The archive is located by searching from the current directory to the root of
103
the filesystem for a directory called 'sandbox_dpkg_archive'.
104
 
105
It is intended that a group of packages that are being developed in the same
106
sandbox will share the same sandbox_dpkg_archive.
107
 
108
Jats will ignore the version number when dealing with packages in GBE_DPKG_SBOX.
109
This is done to simplify the publishing and consuming of packages in the sandbox.
110
 
111
This should not be set by a user. It will be calculated by JATS and passed to
112
JATS tools and utilities.
113
 
114
=item GBE_SANDBOX (optional)
115
 
116
This the path to a sandbox base directory. It is intended that a group of
117
packages that are being developed in the same sandbox will share the same
118
sandbox_dpkg_archive.
119
 
120
This should not be set by a user. It will be calculated by JATS and passed to
121
JATS tools and utilities.
122
 
123
=item GBE_DPLY (optional)
124
 
125
This the path to the deployment archive.
126
This archive will be used when publishing special deployment package. This is
127
not the norm.
128
 
129
This variable may be set on a per-project basis.
130
 
131
=item GBE_PLATFORM (deprecated)
132
 
133
This specifies the names of platforms that will be built and made. This should
134
be empty. Use B<GBE_BUILDFILTER> to provide better control.
135
 
136
=item GBE_BUILDFILTER (desirable)
137
 
138
This is a filter string that specifies which platforms to create makefiles
139
for. This variable is used to prevent JATS from creating Solaris and Linux
140
targets on a Windows machine and visa-versa.
141
 
142
=item GBE_JATS_VERSION (optional)
143
 
144
Specifies the version of JATS that the user will use. This is the same as
145
specifying the -version=xx.xx.xx option on the command line, but because it is
146
in the environment the required version will be used by all invocations of JATS.
147
 
148
=item GBE_ABT (optional)
149
 
150
Used by the Auto Build Tool to indicate that the build is being performed by the
151
ABT. When set the build environment will be modified to suite the ABT. Some
152
operations may be relaxed.
153
 
154
Currently set to 1 to set it.
155
 
156
=item GBE_VIEWBASE (optional)
157
 
158
Used by the 'release' utility to provide a user configurable base directory for
159
the creation of static views.
160
 
161
=item GBE_RM_LOCATION (optional)
162
 
163
Used by tools that interface to Release Manager: primarily the (ABT) Auto Build Tools.
164
Specifies the location of the Release Manager Database. This is a database url
165
of the form jdbc:subprotocol:subname as used by java.sql.DriverManager.getConnection()
166
 
167
C<Example: jdbc:oracle:thin:@auperaora03:1521:RELEASEM>
168
 
169
=item GBE_RM_USERNAME (optional)
170
 
171
Used by tools that interface to Release Manager: primarily the (ABT) Auto Build Tools.
172
Specifies a USERNAME with access to the Release Manager Database.
173
 
174
=item GBE_RM_PASSWORD (optional)
175
 
176
Used by tools that interface to Release Manager: primarily the (ABT) Auto Build Tools.
177
Specifies a PASSWORD to be used in conjunction with GBE_RM_USERNAME to access
178
the Release Manager Database.
179
 
180
=item GBE_RM_URL (optional)
181
 
182
Used by tools that interface to Release Manager: primarily the (ABT) Auto Build Tools.
183
Specifies the base URL of RElease Manager
184
 
185
=item GBE_DM_LOCATION (optional)
186
 
187
Similar to GBE_RM_LOCATION, but is used to access the Deployment Manager Database.
188
If GBE_DM_LOCATION is not provided, then GBE_RM_LOCATION will be used.
189
 
190
=item GBE_DM_USERNAME (optional)
191
 
192
Similar to GBE_RM_USERNAME, but is used to access the Deployment Manager Database.
193
 
194
=item GBE_DM_PASSWORD (optional)
195
 
196
Similar to GBE_RM_PASSWORD, but is used to access the Deployment Manager Database.
197
 
198
=item GBE_DM_URL (optional)
199
 
200
Similar to GBE_DM_URL, but is used to access the Deployment Manager Database.
201
 
341 dpurdie 202
=item GBE_SVN_URL (Required for Subversion support)
315 dpurdie 203
 
341 dpurdie 204
Specifies the URL of the Subversion repository to be used by the Subversion
205
oriented JATS commands. The URL should contain the protocol, the repository
206
host and the path to the root of the repository, but not the name of the
207
repository. ie: C<svn://auperaws996vm21>
315 dpurdie 208
 
209
=item GBE_SVN_PATH (optional)
210
 
211
If provided this will be used to locate the 'svn' utility used by the SubVersion
212
support functions. If not provided, then the utilities assume that 'svn' is in the
341 dpurdie 213
users PATH. 
315 dpurdie 214
 
341 dpurdie 215
Providing the path will prevent JATS from searching for the utility.
216
 
315 dpurdie 217
=item GBE_SVN_USERNAME (optional)
218
 
219
Subversion repository credentials. If provided it will be used, otherwise the
220
native svn credential mechanism will be used.
221
 
222
=item GBE_SVN_PASSWORD (optional)
223
 
224
Subversion repository credentials. If provided it will be used, otherwise the
225
native svn credential mechanism will be used.
226
 
227
=item GBE_MAKE_TYPE (internal)
228
 
229
This EnvVar is set when a Makefile is being processed by 'make'. The value
230
indicates the type of the build. It will be either P(Production), D(debug)
231
or C(Common).
232
 
233
=item GBE_MAKE_TARGET (internal)
234
 
235
This EnvVar is set when a Makefile is being processed by 'make'. The value
236
is set current target platform name.
237
 
238
=item GBE_MAKE_CFG (internal)
239
 
240
This EnvVar is set when a Makefile is being processed by 'make'. The value
241
is set to the path of the parsed makefile.pl data gathered when the makefile
242
was created.
243
 
244
=item GBE_MAKE_CMD (internal)
245
 
246
This EnvVar is set when a Makefile is being processed by 'make'. The value
247
is set current make command being processed.
248
 
249
=item GBE_SCRIPT (internal)
250
 
251
This EnvVar contains the path and comamnd line argument to the current JATS
252
command.
253
 
254
Its primary purpose is to determine the location of the jats startup script:
255
jats.bat or jats.sh.
256
 
257
=item GBE_UNIX (internal)
258
 
259
This EnvVar will be set to 1 on Unix systems and 0 on Windows Systems. The value
260
is calculated by JATS and cannot be set externally.
261
 
262
=item USER (set if undefined)
263
 
264
This EnvVar will be set to the current JATS user. It may be set externally,
265
but normally this is not required as JATS will determine the user in a
266
platform specific manner.
267
 
268
=back
269
 
270
=head2 Location of EnvVar definitions
271
 
272
The location of the EnvVars used by JATS is dependent on the target machine
273
type.
274
 
275
=head3 Windows 
276
 
277
Under Windows, the best place to specify the JATS EnvVars is in the JATS.BAT
278
file itself. The location of the JATS.BAT file being used is provided by the '
279
jats vars' utility.
280
 
281
=head3 Solaris
282
 
283
Under Solaris, the JATS EnvVars are set in /etc/profile. These can be
284
overridden by users in there own profile, but this is not encouraged as the
285
JATS configuration is normally machine-wide.
286
 
287
The jats.sh script, used to start jats may provide deafult definitions. The
288
location of this script is provided by the 'jats vars' utility.
289
 
290
=head3 Linux
291
 
292
Under Linux, the JATS EnvVars are set in  /etc/profile.d/jats.sh. These can be
293
overridden by users in there own profile, but this is not encouraged as the
294
JATS configuration is normally machine-wide.
295
 
296
The jats.sh script, used to start jats may provide deafult definitions. The
297
location of this script is provided by the 'jats vars' utility.
298