git.iko.soy/stackage
on 1237b89 help sign in
stackage/automated/build.sh
147 lines 6.4 kB history raw
1#!/usr/bin/env bash
3set -eu +x
5ROOT=$(cd $(dirname $0) ; pwd)
6TARGET=$1
8source aws.sh
10# For nightly-YYYY-MM-DD, tag should be nightly
11# For lts-X.Y, tag should be ltsX
12SHORTNAME=$(echo $TARGET | cut -d- -f 1)
13if [ $SHORTNAME = "lts" ]
14then
15 TAG=$(echo $TARGET | sed 's@^lts-\([0-9]*\)\.[0-9]*@lts\1@')
16else
17 TAG=$SHORTNAME
18fi
20IMAGE=commercialhaskell/stackage:$TAG
22PLAN_FILE=current-plan.yaml
23DOCMAP_FILE=current-docmap.yaml
25CABAL_DIR=$ROOT/cabal
26STACK_DIR=$ROOT/stack
27GHC_DIR=$ROOT/ghc
28DOT_STACKAGE_DIR=$ROOT/dot-stackage
29WORKDIR=$ROOT/$TAG/work
30EXTRA_BIN_DIR=$ROOT/extra-bin
31SSH_DIR=$ROOT/ssh-$SHORTNAME
32USERID=$(id -u)
34mkdir -p \
35 "$CABAL_DIR" \
36 "$STACK_DIR" \
37 "$GHC_DIR" \
38 "$DOT_STACKAGE_DIR" \
39 "$WORKDIR" \
40 "$EXTRA_BIN_DIR" \
41 "$SSH_DIR"
43GITCONFIG=$ROOT/gitconfig
44cat >$GITCONFIG <<EOF
45[user]
46 email = michael+stackage-build@fpcomplete.com
47 name = Stackage Build host
48EOF
50cat >$SSH_DIR/known_hosts <<EOF
51|1|Qn0iij8BnxGZXbyFSozS9zWkH+Q=|YrKKNp2KHO3/oc4UBFIe1zOvhDc= ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ==
52|1|RxBEt2ljiEppr019szMIhbY12m0=|0FZ2Oji1LphRbPLLEQhFzTmL69I= ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ==
53EOF
55AUTH_TOKEN=$ROOT/auth-token
56HACKAGE_CREDS=$ROOT/hackage-creds
58function require_400_file {
59 if [ ! -f "$1" ]
60 then
61 echo File not found: "$1"
62 exit 1
63 fi
65 chmod 400 "$1"
68require_400_file "$SSH_DIR/id_rsa"
69require_400_file "$AUTH_TOKEN"
70require_400_file "$HACKAGE_CREDS"
72mkdir -p $ROOT/bin
73BINDIR=$(cd $ROOT/bin ; pwd)
75cd $BINDIR
76rm -f stackage-curator stackage-curator.bz2
77wget https://s3.amazonaws.com/stackage-travis/stackage-curator/stackage-curator.bz2
78bunzip2 stackage-curator.bz2
79chmod +x stackage-curator
80./stackage-curator --version
83ARGS_COMMON="--rm -v $WORKDIR:$HOME/work -w $HOME/work -v $BINDIR/stackage-curator:/usr/bin/stackage-curator:ro -v /etc/passwd:/etc/passwd:ro -v /etc/group:/etc/group:ro -v $EXTRA_BIN_DIR/stack:/usr/bin/stack:ro"
84ARGS_PREBUILD="$ARGS_COMMON -u $USERID -e HOME=$HOME -v $CABAL_DIR:$HOME/.cabal -v $STACK_DIR:$HOME/.stack -v $GHC_DIR:$HOME/.ghc -v $DOT_STACKAGE_DIR:$HOME/.stackage"
85ARGS_BUILD="$ARGS_COMMON -v $CABAL_DIR:$HOME/.cabal:ro -v $STACK_DIR:$HOME/.stack:ro -v $GHC_DIR:$HOME/.ghc:ro"
86ARGS_UPLOAD="$ARGS_COMMON -u $USERID -e HOME=$HOME -e AWS_ACCESS_KEY_ID=$AWS_ACCESS_KEY_ID -e AWS_SECRET_ACCESS_KEY=$AWS_SECRET_ACCESS_KEY -v $AUTH_TOKEN:/auth-token:ro -v $HACKAGE_CREDS:/hackage-creds:ro -v $DOT_STACKAGE_DIR:$HOME/.stackage -v $SSH_DIR:$HOME/.ssh:ro -v $GITCONFIG:$HOME/.gitconfig:ro -v $CABAL_DIR:$HOME/.cabal:ro -v $STACK_DIR:$HOME/.stack:ro"
88# Make sure we actually need this snapshot. We only check this for LTS releases
89# since, for nightlies, we'd like to run builds even if they are unnecessary to
90# get early warning information of upcoming failures. (See the duplicate check
91# below for why this is safe.)
92if [ $SHORTNAME = "lts" ]
93then
94 docker run $ARGS_UPLOAD $IMAGE /bin/bash -c "exec stackage-curator check-target-available --target $TARGET"
95fi
97# Get latest stack
98curl -L https://www.stackage.org/stack/linux-x86_64 | tar xz --wildcards --strip-components=1 -C $EXTRA_BIN_DIR '*/stack'
100# Determine the new build plan unless NOPLAN is set
102# * Update the package index (unless LTS)
103# * Create a new plan
104if [ "${NOPLAN:-}x" = "x" ]
105then
106 if [ $SHORTNAME = "lts" ]
107 then
108 docker run $ARGS_PREBUILD $IMAGE /bin/bash -c "exec stackage-curator create-plan --plan-file $PLAN_FILE --target $TARGET ${CONSTRAINTS:-}"
109 else
110 docker run $ARGS_PREBUILD $IMAGE /bin/bash -c "stack update && exec stackage-curator create-plan --plan-file $PLAN_FILE --target $TARGET ${CONSTRAINTS:-}"
111 fi
112fi
114# Do the rest of the pre-build actions:
116# * Check that the plan is valid
117# * Fetch all needed tarballs (the build step does not have write access to the tarball directory)
118# * Do a single unpack to create the package index cache (again due to directory perms)
119docker run $ARGS_PREBUILD $IMAGE /bin/bash -c "stackage-curator check --plan-file $PLAN_FILE && stackage-curator fetch --plan-file $PLAN_FILE && cd /tmp && exec stack unpack random"
121case $SHORTNAME in
122 lts) JOBS=1 ;;
123 nightly) JOBS=2 ;;
124esac
126# Now do the actual build. We need to first set the owner of the home directory
127# correctly, so we run the command as root, change owner, and then use sudo to
128# switch back to the current user
129docker run $ARGS_BUILD $IMAGE nice -n 15 /bin/bash -c "chown $USER $HOME && exec sudo -E -u $USER env \"HOME=$HOME\" \"PATH=\$PATH\" stackage-curator make-bundle --jobs $JOBS --plan-file $PLAN_FILE --docmap-file $DOCMAP_FILE --target $TARGET"
131# Make sure we actually need this snapshot. We used to perform this check
132# exclusively before building. Now we perform it after as well for the case of
133# nightly, where we don't perform this check beforehand. This is also slightly
134# safer, in case someone else already uploaded a specific snapshot while we
135# were building.
136docker run $ARGS_UPLOAD $IMAGE /bin/bash -c "exec stackage-curator check-target-available --target $TARGET"
138# Successful build, so we need to:
140# * Upload the docs to S3
141# * Upload the 00-index.tar file to S3 (TODO: this is probably no longer necessary, since snapshots never modify .cabal files)
142# * Upload the new plan .yaml file to the appropriate Github repo
143# * Register as a new Hackage distro
144docker run $ARGS_UPLOAD $IMAGE /bin/bash -c "stackage-curator upload-docs --target $TARGET && stackage-curator upload-index --plan-file $PLAN_FILE --target $TARGET && stackage-curator upload-github --plan-file $PLAN_FILE --docmap-file $DOCMAP_FILE --target $TARGET && exec stackage-curator hackage-distro --plan-file $PLAN_FILE --target $TARGET"
146echo -n "Completed at "
147date