Subversion Repositories DevTools

Rev

Rev 7322 | Details | Compare with Previous | Last modification | View Log | RSS feed

Rev Author Line No. Line
315 dpurdie 1
#-------------------------------------------------------------------------------
2
#   Documentation
3
#
4
 
5
=pod
6
 
361 dpurdie 7
=for htmltoc    CORE::
8
 
315 dpurdie 9
=head1 NAME
10
 
11
JATS Environment Variables
12
 
13
=head1 SYNOPSIS
14
 
15
JATS makes use of a number of Environment Variables (EnvVars) to provide
16
configuration information.
17
 
18
There are two classes of EnvVars used by JATS. These are:
19
 
361 dpurdie 20
=over 4
315 dpurdie 21
 
361 dpurdie 22
=item 1 
315 dpurdie 23
 
361 dpurdie 24
JATS Configuration
25
 
315 dpurdie 26
These EnvVars have a GBE_ prefix. These are detailed in this document.
27
 
361 dpurdie 28
=item 2 
315 dpurdie 29
 
361 dpurdie 30
Toolset location
31
 
315 dpurdie 32
Some of the build tools used by JATS use EnvVars to specify the location
33
of the installed tool. 
34
 
35
Ideally tools should be installed in their default location and JATS should be
36
preconfigured to use this default location. Configuration allows for exceptions.
37
 
38
=back
39
 
40
=head2  Environment variables
41
 
42
Environment variables that specify a path may be set to '-', or 'none' in order
43
to force an undefined path.
44
 
45
=over 8
46
 
47
=item GBE_MACHTYPE
48
 
49
This specifies the machine that the script is running on. This is fixed within
50
the startup script.
51
 
52
=item GBE_HOSTMACH (internally set)
53
 
54
This is a copy of GBE_MACHTYPE.
55
Unlike GBE_MACHTYPE, this copy is not modified by makefiles.
56
 
57
=item GBE_HOSTNAME (internally)
58
 
59
This EnvVar is the name of the current host. It is available to be used within
60
scripts that need to stamp build files.
61
 
62
=item GBE_PERL
63
 
64
This specifies the full path the to B<ActiveState> perl binary.
65
 
66
=item GBE_CORE
67
 
68
This specifies the path the to B<JATS> installation.
69
 
70
=item GBE_CACHE_JATS
71
 
72
When set to a non zero value will force JATS to transfer a working copy to the
73
local dpkg_archive. This will speed up the build process because the utilities
74
will be run from a local drive; not a network drive.
75
 
76
This will only operate if JATS is run from dpkg_archive.
77
 
78
=item GBE_DPKG_STORE (optional)
79
 
80
This is the global read-only archive store. It will only be used to source
81
packages after all other archive stores have been examined. The GBE_DPKG_STORE
82
is intended to provide a read-only or remote repository within a global
83
environment.
84
 
85
=item GBE_DPKG
86
 
87
This is the official archive. Some tools will publish packages directly to this
88
archive.
89
 
90
This item is mandatory and must address a valid directory.
91
 
4688 dpurdie 92
=item GBE_DPKG_REPLICA (optional)
93
 
94
This is the local package read-only archive replica. It will only be used to source
95
packages before other archive stores have been examined. The GBE_DPKG_REPLICA
96
is intended to provide a local read-only replica of the main repository within a global
97
environment.
98
 
315 dpurdie 99
=item GBE_DPKG_CACHE (optional)
100
 
101
This the path to a local package archive cache. This is used to speed access to
102
main repository. The cache should be on the users local machine and not a network
103
drive.
104
 
5109 dpurdie 105
=item GBE_DPKG_CACHE_CTL (optional)
106
 
107
Controls the automatic population of GBE_DPKG_CACHE, if it is defined. The provided value
108
is used as the initial value for the build argument of '-cache'.
109
 
110
The following values are supported:
111
 
112
=over 4
113
 
114
=item 0 - Do not cache package versions.
115
 
116
This is the default mode of operation. Caching can still be controlled from the
117
comamdn line of the 'build' command.
118
 
119
=item 1 - Cache package versions. 
120
 
121
If version is not present in the cache, then it will be transferred.
122
 
123
=item 2 - Force caching of package versions. 
124
 
125
Will transfer the package even if it already exists in the cache. Not recommended.
126
 
127
=back
128
 
315 dpurdie 129
=item GBE_DPKG_LOCAL (optional)
130
 
131
This the path to a group wide local package archive. This may be used to store
132
non-official packages that are under test or development.
133
 
343 dpurdie 134
Not recommended. Use is being deprecated.
315 dpurdie 135
 
7319 dpurdie 136
=item GBE_DPKG_ESCROW (optional)
137
 
138
This the path to directory used in escrow builds to assemble the parts of the various
139
builds.
140
 
141
The presence of this value will alter the normal package search processing such that
142
most of the package archives are not searched. The only archives that will be searched are:
143
 
144
=over 4
145
 
146
* GBE_DPKG_SANDBOX
147
 
148
* GBE_DPKG_LOCAL
149
 
150
* GBE_DPKG_CACHE
151
 
152
* GBE_DPKG_ESCROW
153
 
154
=back
155
 
156
Used only in an escrow build. Care must be taken to ensure that all the package stores
157
are empty before the escrow build process is initiated.
158
 
343 dpurdie 159
=item GBE_DPKG_SBOX (internal)
160
 
161
This the path to a sandbox specific package archive. This will be used to store
315 dpurdie 162
non-official packages that are under test or development within the current sandbox.
163
 
164
The archive is located by searching from the current directory to the root of
343 dpurdie 165
the file system for a directory called 'sandbox_dpkg_archive'.
315 dpurdie 166
 
167
It is intended that a group of packages that are being developed in the same
168
sandbox will share the same sandbox_dpkg_archive.
169
 
170
Jats will ignore the version number when dealing with packages in GBE_DPKG_SBOX.
171
This is done to simplify the publishing and consuming of packages in the sandbox.
172
 
173
This should not be set by a user. It will be calculated by JATS and passed to
174
JATS tools and utilities.
175
 
343 dpurdie 176
=item GBE_SANDBOX (internal)
315 dpurdie 177
 
178
This the path to a sandbox base directory. It is intended that a group of
179
packages that are being developed in the same sandbox will share the same
180
sandbox_dpkg_archive.
181
 
182
This should not be set by a user. It will be calculated by JATS and passed to
183
JATS tools and utilities.
184
 
7323 dpurdie 185
=item GBE_SANDBOX_BUILD (internal)
186
 
187
This EnvVar will contain a non-zero value when commands are executed by
188
'jats sandbox'. This allows some tools to operate correctly within a sandbox
189
environment.
190
 
191
The initial tool is 'gradle'. The command line build will prevent gradle from
192
building dependent packagses as they are built by the sandbox process.
193
 
315 dpurdie 194
=item GBE_DPLY (optional)
195
 
196
This the path to the deployment archive.
197
This archive will be used when publishing special deployment package. This is
198
not the norm.
199
 
200
This variable may be set on a per-project basis.
201
 
202
=item GBE_PLATFORM (deprecated)
203
 
204
This specifies the names of platforms that will be built and made. This should
205
be empty. Use B<GBE_BUILDFILTER> to provide better control.
206
 
207
=item GBE_BUILDFILTER (desirable)
208
 
209
This is a filter string that specifies which platforms to create makefiles
210
for. This variable is used to prevent JATS from creating Solaris and Linux
211
targets on a Windows machine and visa-versa.
212
 
213
=item GBE_JATS_VERSION (optional)
214
 
215
Specifies the version of JATS that the user will use. This is the same as
216
specifying the -version=xx.xx.xx option on the command line, but because it is
217
in the environment the required version will be used by all invocations of JATS.
218
 
219
=item GBE_ABT (optional)
220
 
221
Used by the Auto Build Tool to indicate that the build is being performed by the
222
ABT. When set the build environment will be modified to suite the ABT. Some
223
operations may be relaxed.
224
 
225
Currently set to 1 to set it.
226
 
4902 dpurdie 227
Used values:
228
 
229
=over 4
230
 
231
=item NONE
232
 
233
Indicates that the current machine is not to be used to build software. It may be used to run various JATS utilities.
234
 
235
=back
236
 
3859 dpurdie 237
=item ANT_HOME (desirable)
238
 
239
Used by the Auto Build Tool and any JATS builds that make use of ANT. This 
240
EnvVar should specify the location of the root of the ANT (1.6.5) Installation. 
241
Jats will expect to locate 'bin/ant' below ANT_HOME.
242
 
315 dpurdie 243
=item GBE_VIEWBASE (optional)
244
 
343 dpurdie 245
Used by the 'release' utilities to provide a user configurable base directory for
246
the creation of static views. The default location is:
315 dpurdie 247
 
343 dpurdie 248
=over 8
249
 
361 dpurdie 250
=item *
343 dpurdie 251
 
361 dpurdie 252
WINDOWS - c:\clearcase
343 dpurdie 253
 
361 dpurdie 254
=item * 
255
 
256
Unix - ${HOME}/jats_cbuilder
257
 
343 dpurdie 258
=back
259
 
361 dpurdie 260
=item GBE_VCS (optional)
261
 
262
Used by the JATS wrapper script when processing the 'release', 'extract' and 'label'
263
commands to determine the command to invoke.
264
 
265
If not specified, then 'cc' is assumed.
266
 
267
Valid values are:
268
 
269
=over 4
270
 
271
=item *
272
 
273
cc for ClearCase
274
 
275
=item *
276
 
277
svn for Subversion
278
 
279
=back
280
 
315 dpurdie 281
=item GBE_RM_LOCATION (optional)
282
 
283
Used by tools that interface to Release Manager: primarily the (ABT) Auto Build Tools.
284
Specifies the location of the Release Manager Database. This is a database url
285
of the form jdbc:subprotocol:subname as used by java.sql.DriverManager.getConnection()
286
 
4466 dpurdie 287
C<Example: jdbc:oracle:thin:@auperaprm01:1521:RELEASEM>
315 dpurdie 288
 
289
=item GBE_RM_USERNAME (optional)
290
 
291
Used by tools that interface to Release Manager: primarily the (ABT) Auto Build Tools.
292
Specifies a USERNAME with access to the Release Manager Database.
293
 
294
=item GBE_RM_PASSWORD (optional)
295
 
296
Used by tools that interface to Release Manager: primarily the (ABT) Auto Build Tools.
297
Specifies a PASSWORD to be used in conjunction with GBE_RM_USERNAME to access
298
the Release Manager Database.
299
 
300
=item GBE_RM_URL (optional)
301
 
302
Used by tools that interface to Release Manager: primarily the (ABT) Auto Build Tools.
303
Specifies the base URL of RElease Manager
304
 
305
=item GBE_DM_LOCATION (optional)
306
 
307
Similar to GBE_RM_LOCATION, but is used to access the Deployment Manager Database.
308
If GBE_DM_LOCATION is not provided, then GBE_RM_LOCATION will be used.
309
 
310
=item GBE_DM_USERNAME (optional)
311
 
312
Similar to GBE_RM_USERNAME, but is used to access the Deployment Manager Database.
313
 
314
=item GBE_DM_PASSWORD (optional)
315
 
316
Similar to GBE_RM_PASSWORD, but is used to access the Deployment Manager Database.
317
 
318
=item GBE_DM_URL (optional)
319
 
320
Similar to GBE_DM_URL, but is used to access the Deployment Manager Database.
321
 
4466 dpurdie 322
=item GBE_CQ_LOCATION (optional)
323
 
324
Used by tools that interface to ClearQuest: primarily the (ABT) Auto Build Tools.
325
Specifies the location of the ClearQuest Database. This is a database url
326
of the form jdbc:subprotocol:subname as used by java.sql.DriverManager.getConnection()
327
 
328
C<Example: jdbc:jtds:sqlserver://AUPERASQL05:1433:master>
329
 
330
=item GBE_CQ_USERNAME (optional)
331
 
332
Used by tools that interface to ClearQuest: primarily the (ABT) Auto Build Tools.
333
Specifies a USERNAME with access to the ClearQuest Database.
334
 
335
=item GBE_CQ_PASSWORD (optional)
336
 
337
Used by tools that interface to ClearQuest: primarily the (ABT) Auto Build Tools.
338
Specifies a PASSWORD to be used in conjunction with GBE_RM_USERNAME to access
339
the ClearQuest Database.
340
 
4612 dpurdie 341
=item GBE_JIRA_URL (optonal)
342
 
343
Used by tools that interface to the Jira Issues database via a REST API: primarily the
344
Auto Build Tools. The variable specifies the URL to the base of the REST API interface.
345
 
5254 dpurdie 346
C<Example: http://cds.vixtechnology.com:443>
4612 dpurdie 347
 
348
=item GBE_JIRA_USERNAME (optional)
349
 
350
Using in conjunction with GBE_JIRA_URL to access the Jira Issues database.
351
 
352
=item GBE_JIRA_PASSWORD (optional)
353
 
354
Using in conjunction with GBE_JIRA_URL to access the Jira Issues database.
355
 
353 dpurdie 356
=item GBE_SVN_URL_<Repo> (Required for Subversion support)
357
 
358
Provides subversion configuration of known repositories. The EnvVar contains 
5710 dpurdie 359
the unique name of the repository within the VIX domain. ie: 
353 dpurdie 360
C<GBE_SVN_URL_AUPERASVN01>
361
 
362
The value of the EnvVar specifies the URL of the Subversion repository to be
363
used by the Subversion oriented JATS commands. The URL should contain the
364
protocol, the repository host and the path to the root of the repository and
4814 dpurdie 365
possibly name of the repository. ie: C<https://auawsasvn001.vix.local/svn>
353 dpurdie 366
 
341 dpurdie 367
=item GBE_SVN_URL (Required for Subversion support)
315 dpurdie 368
 
353 dpurdie 369
Specifies the default URL of the Subversion repository to be used by the
370
Subversion oriented JATS commands. The URL should contain the protocol, the
371
repository host and the path to the root of the repository, but not the name of
4814 dpurdie 372
the repository. ie: C<https://auawsasvn001.vix.local/svn>
315 dpurdie 373
 
353 dpurdie 374
This EnvVar is similar to B<GBE_SVN_URL_<Repo>>, except that it will only be
375
used as a last resort. It may be used to provide a site wide repository URL, but
376
it would not be suitable for repositories that are external to the site. 
377
 
378
For correct operation of utilities that calculate a global Subversion tag,
379
B<GBE_SVN_URL> should resolve to one of B<GBE_SVN_URL_<Repo>> values.
380
 
315 dpurdie 381
=item GBE_SVN_PATH (optional)
382
 
383
If provided this will be used to locate the 'svn' utility used by the SubVersion
384
support functions. If not provided, then the utilities assume that 'svn' is in the
341 dpurdie 385
users PATH. 
315 dpurdie 386
 
341 dpurdie 387
Providing the path will prevent JATS from searching for the utility.
388
 
315 dpurdie 389
=item GBE_SVN_USERNAME (optional)
390
 
391
Subversion repository credentials. If provided it will be used, otherwise the
392
native svn credential mechanism will be used.
393
 
394
=item GBE_SVN_PASSWORD (optional)
395
 
396
Subversion repository credentials. If provided it will be used, otherwise the
397
native svn credential mechanism will be used.
398
 
5695 dpurdie 399
=item GBE_MAXMAKE (optional)
400
 
401
If defined this value will specify the default MaxTime used by the Jats Make utility.
402
 
403
Refer the '-MaxTime' option in the 'L<make|TOOLS::jmake>' utility for details.
404
 
315 dpurdie 405
=item GBE_MAKE_TYPE (internal)
406
 
407
This EnvVar is set when a Makefile is being processed by 'make'. The value
408
indicates the type of the build. It will be either P(Production), D(debug)
409
or C(Common).
410
 
411
=item GBE_MAKE_TARGET (internal)
412
 
413
This EnvVar is set when a Makefile is being processed by 'make'. The value
414
is set current target platform name.
415
 
416
=item GBE_MAKE_CFG (internal)
417
 
418
This EnvVar is set when a Makefile is being processed by 'make'. The value
419
is set to the path of the parsed makefile.pl data gathered when the makefile
420
was created.
421
 
422
=item GBE_MAKE_CMD (internal)
423
 
424
This EnvVar is set when a Makefile is being processed by 'make'. The value
425
is set current make command being processed.
426
 
4949 dpurdie 427
=item GBE_UTFNAME (internal)
428
 
429
This EnvVar is set when a unit test is being run. It is the name of the unit test.
430
 
431
=item GBE_UTFUID (internal)
432
 
433
This EnvVar is set when a unit test is being run. It is a short string that will 
434
uniquely identify the unit test within the build. It may be used to create a unique
435
log file for post processing.
436
 
4996 dpurdie 437
=item GBE_UTFFILE (internal)
438
 
439
This EnvVar is set when a unit test is being run. It is an absolute path to a
440
recommended output file within the final package. 
441
 
7322 dpurdie 442
It will be unique as it includes the GBE_UTFUID element. Unit Tests may 
4996 dpurdie 443
create correctly formatted test results in this file.
444
 
7322 dpurdie 445
=item GBE_UTFTEST (internal)
446
 
447
This EnvVar is set when a unit test is being run. It a part of a file name that may be used
448
to construct an output file for the tests.  
449
 
450
Some unit tests filters require files that start with this name and have a 
451
suitable extension. The file extension is not provided.
452
 
453
The name will be unique.
454
 
315 dpurdie 455
=item GBE_SCRIPT (internal)
456
 
343 dpurdie 457
This EnvVar contains the path and command line argument to the current JATS
315 dpurdie 458
command.
459
 
460
Its primary purpose is to determine the location of the jats startup script:
461
jats.bat or jats.sh.
462
 
463
=item GBE_UNIX (internal)
464
 
465
This EnvVar will be set to 1 on Unix systems and 0 on Windows Systems. The value
466
is calculated by JATS and cannot be set externally.
467
 
468
=item USER (set if undefined)
469
 
470
This EnvVar will be set to the current JATS user. It may be set externally,
471
but normally this is not required as JATS will determine the user in a
472
platform specific manner.
473
 
474
=back
475
 
476
=head2 Location of EnvVar definitions
477
 
478
The location of the EnvVars used by JATS is dependent on the target machine
479
type.
480
 
481
=head3 Windows 
482
 
483
Under Windows, the best place to specify the JATS EnvVars is in the JATS.BAT
484
file itself. The location of the JATS.BAT file being used is provided by the '
485
jats vars' utility.
486
 
487
=head3 Solaris
488
 
489
Under Solaris, the JATS EnvVars are set in /etc/profile. These can be
490
overridden by users in there own profile, but this is not encouraged as the
491
JATS configuration is normally machine-wide.
492
 
343 dpurdie 493
The jats.sh script, used to start jats may provide default definitions. The
315 dpurdie 494
location of this script is provided by the 'jats vars' utility.
495
 
496
=head3 Linux
497
 
498
Under Linux, the JATS EnvVars are set in  /etc/profile.d/jats.sh. These can be
499
overridden by users in there own profile, but this is not encouraged as the
500
JATS configuration is normally machine-wide.
501
 
343 dpurdie 502
The jats.sh script, used to start jats may provide default definitions. The
315 dpurdie 503
location of this script is provided by the 'jats vars' utility.
504