|
7 | 7 |
|
8 | 8 | echo "nightly_defaults.sh at $(pwd) starting at $(date) on $(uname -a) with pid $$" |
9 | 9 |
|
10 | | -# List of people to email when things go wrong. This is passed directly to |
11 | | -# `mail -t` |
12 | | -export NIGHTLIES_EMAIL_LIST= '[email protected]' |
13 | | - |
14 | | -# PYTORCH_CREDENTIALS_FILE |
15 | | -# A bash file that exports credentials needed to upload to aws and anaconda. |
16 | | -# Needed variables are PYTORCH_ANACONDA_USERNAME, PYTORCH_ANACONDA_PASSWORD, |
17 | | -# AWS_ACCESS_KEY_ID, and AWS_SECRET_ACCESS_KEY. Or it can just export the AWS |
18 | | -# keys and then prepend a logged-in conda installation to the path. |
19 | | -if [[ -z "$PYTORCH_CREDENTIALS_FILE" ]]; then |
20 | | - if [[ "$(uname)" == 'Darwin' ]]; then |
21 | | - export PYTORCH_CREDENTIALS_FILE='/Users/administrator/nightlies/credentials.sh' |
22 | | - else |
23 | | - export PYTORCH_CREDENTIALS_FILE='/private/home/hellemn/nightly_credentials.sh' |
24 | | - fi |
25 | | -fi |
26 | | - |
27 | | -# Location of the temporary miniconda that is downloaded to install conda-build |
28 | | -# and aws to upload finished packages TODO this is messy to install this in |
29 | | -# upload.sh and later use it in upload_logs.sh |
30 | | -CONDA_UPLOADER_INSTALLATION="${today}/miniconda" |
31 | | - |
32 | 10 | # NIGHTLIES_FOLDER |
33 | 11 | # N.B. this is also defined in cron_start.sh |
34 | 12 | # An arbitrary root folder to store all nightlies folders, each of which is a |
|
70 | 48 | export today="$NIGHTLIES_FOLDER/$NIGHTLIES_DATE" |
71 | 49 | mkdir -p "$today" || true |
72 | 50 |
|
| 51 | + |
| 52 | +############################################################################## |
| 53 | +# Add new configuration variables below this line. 'today' should always be |
| 54 | +# defined ASAP to avoid weird errors |
| 55 | +############################################################################## |
| 56 | + |
| 57 | + |
| 58 | +# List of people to email when things go wrong. This is passed directly to |
| 59 | +# `mail -t` |
| 60 | +export NIGHTLIES_EMAIL_LIST= '[email protected]' |
| 61 | + |
| 62 | +# PYTORCH_CREDENTIALS_FILE |
| 63 | +# A bash file that exports credentials needed to upload to aws and anaconda. |
| 64 | +# Needed variables are PYTORCH_ANACONDA_USERNAME, PYTORCH_ANACONDA_PASSWORD, |
| 65 | +# AWS_ACCESS_KEY_ID, and AWS_SECRET_ACCESS_KEY. Or it can just export the AWS |
| 66 | +# keys and then prepend a logged-in conda installation to the path. |
| 67 | +if [[ -z "$PYTORCH_CREDENTIALS_FILE" ]]; then |
| 68 | + if [[ "$(uname)" == 'Darwin' ]]; then |
| 69 | + export PYTORCH_CREDENTIALS_FILE='/Users/administrator/nightlies/credentials.sh' |
| 70 | + else |
| 71 | + export PYTORCH_CREDENTIALS_FILE='/private/home/hellemn/nightly_credentials.sh' |
| 72 | + fi |
| 73 | +fi |
| 74 | + |
| 75 | +# Location of the temporary miniconda that is downloaded to install conda-build |
| 76 | +# and aws to upload finished packages TODO this is messy to install this in |
| 77 | +# upload.sh and later use it in upload_logs.sh |
| 78 | +CONDA_UPLOADER_INSTALLATION="${today}/miniconda" |
| 79 | + |
73 | 80 | # N.B. BUILDER_REPO and BUILDER_BRANCH are both set in cron_start.sh, as that |
74 | 81 | # is the script that actually clones the builder repo that /this/ script is |
75 | 82 | # running from. |
|
0 commit comments