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