66 CLONE_WS="ssh://anonhg@onnv.sfbay.sun.com//export/onnv-clone"; export CLONE_WS
67
68 # CLOSED_CLONE_WS is the workspace from which nightly will acquire the
69 # usr/closed tree.
70 CLOSED_CLONE_WS="${CLONE_WS}/usr/closed"
71 export CLOSED_CLONE_WS
72
73 # The bringover, if any, is done as STAFFER.
74 # Set STAFFER to your own login as gatekeeper or integration engineer.
75 # The point is to use group "staff" and avoid referencing the parent
76 # workspace as root.
77 # Some scripts optionally send mail messages to MAILTO.
78 #
79 STAFFER=nobody; export STAFFER
80 MAILTO=$STAFFER; export MAILTO
81
82 # The project (see project(4)) under which to run this build. If not
83 # specified, the build is simply run in a new task in the current project.
84 BUILD_PROJECT=; export BUILD_PROJECT
85
86 # You should not need to change the next four lines
87 LOCKNAME="`basename $CODEMGR_WS`_nightly.lock"; export LOCKNAME
88 ATLOG="$CODEMGR_WS/log"; export ATLOG
89 LOGFILE="$ATLOG/nightly.log"; export LOGFILE
90 MACH=`uname -p`; export MACH
91
92 # When the -A flag is specified, and ELF_DATA_BASELINE_DIR is defined,
93 # the ELF interface description file resulting from the build is compared
94 # to that from the specified directory. This ensures that our object
95 # versioning evolves in a backward compatible manner.
96 #
97 # You should not need to change this unless you wish to use locally cached
98 # baseline files. If you use this, it must be local (or nfs): nightly cannot
99 # copy over ssh or http.
100 #
101 ELF_DATA_BASELINE_DIR="/ws/onnv-gate/usr/src/ELF-data-baseline.$MACH"; export ELF_DATA_BASELINE_DIR
102
103 # This is usually just needed if the closed tree is missing, or when
104 # building a project gate with the -O (cap oh) flag.
105 # ON_CRYPTO_BINS="$PARENT_WS/packages/$MACH/on-crypto.$MACH.tar.bz2"
106 # export ON_CRYPTO_BINS
107
|
66 CLONE_WS="ssh://anonhg@onnv.sfbay.sun.com//export/onnv-clone"; export CLONE_WS
67
68 # CLOSED_CLONE_WS is the workspace from which nightly will acquire the
69 # usr/closed tree.
70 CLOSED_CLONE_WS="${CLONE_WS}/usr/closed"
71 export CLOSED_CLONE_WS
72
73 # The bringover, if any, is done as STAFFER.
74 # Set STAFFER to your own login as gatekeeper or integration engineer.
75 # The point is to use group "staff" and avoid referencing the parent
76 # workspace as root.
77 # Some scripts optionally send mail messages to MAILTO.
78 #
79 STAFFER=nobody; export STAFFER
80 MAILTO=$STAFFER; export MAILTO
81
82 # The project (see project(4)) under which to run this build. If not
83 # specified, the build is simply run in a new task in the current project.
84 BUILD_PROJECT=; export BUILD_PROJECT
85
86 # You should not need to change the next three lines
87 ATLOG="$CODEMGR_WS/log"; export ATLOG
88 LOGFILE="$ATLOG/nightly.log"; export LOGFILE
89 MACH=`uname -p`; export MACH
90
91 # When the -A flag is specified, and ELF_DATA_BASELINE_DIR is defined,
92 # the ELF interface description file resulting from the build is compared
93 # to that from the specified directory. This ensures that our object
94 # versioning evolves in a backward compatible manner.
95 #
96 # You should not need to change this unless you wish to use locally cached
97 # baseline files. If you use this, it must be local (or nfs): nightly cannot
98 # copy over ssh or http.
99 #
100 ELF_DATA_BASELINE_DIR="/ws/onnv-gate/usr/src/ELF-data-baseline.$MACH"; export ELF_DATA_BASELINE_DIR
101
102 # This is usually just needed if the closed tree is missing, or when
103 # building a project gate with the -O (cap oh) flag.
104 # ON_CRYPTO_BINS="$PARENT_WS/packages/$MACH/on-crypto.$MACH.tar.bz2"
105 # export ON_CRYPTO_BINS
106
|