#!/usr/bin/env bash set -eu +x -o pipefail ROOT=$(cd $(dirname $0) ; pwd) TARGET=$1 source work/aws.sh # For nightly-YYYY-MM-DD, tag should be nightly # For lts-X.Y, tag should be ltsX SHORTNAME=$(echo $TARGET | cut -d- -f 1) if [ $SHORTNAME = "lts" ] then TAG=$(echo $TARGET | sed 's@^lts-\([0-9]*\)\.[0-9]*@lts\1@') WORKDIR=$ROOT/work/$(echo $TARGET | sed 's@^lts-\([0-9]*\)\.[0-9]*@lts-\1@') else TAG=$SHORTNAME WORKDIR=$ROOT/work/$TAG fi #IMAGE=commercialhaskell/stackage:$TAG IMAGE=ghcr.io/commercialhaskell/stackage/build:$TAG PANTRY_DIR=$ROOT/work/stack/pantry STACK_DIR=$ROOT/work/stack DOT_STACKAGE_DIR=$ROOT/work/dot-stackage # ssh key is used for committing snapshots (and their constraints) to Github SSH_DIR=$ROOT/work/ssh USERID=$(id -u) mkdir -p \ "$PANTRY_DIR" \ "$STACK_DIR" \ "$DOT_STACKAGE_DIR" \ "$WORKDIR" \ "$SSH_DIR" GITCONFIG=$ROOT/work/gitconfig cat >$GITCONFIG < curator chmod +x curator echo -n "curator version: " docker run --rm -v $(pwd)/curator:/exe $IMAGE /exe --version STACK_VERSION=2.11.1 curl -L https://github.com/commercialhaskell/stack/releases/download/v${STACK_VERSION}/stack-${STACK_VERSION}-linux-x86_64-bin > stack chmod +x stack echo -n "stack version: " docker run --rm -v $(pwd)/stack:/exe $IMAGE /exe --version ) # We share pantry directory between snapshots while the other content in .stack # is stored separately (because e.g. Ubuntu releases between LTS and nightly # could differ). Also the order of binds is important. ARGS_COMMON="--rm -v $WORKDIR:$HOME/work -w $HOME/work -v $BINDIR/curator:/usr/bin/curator:ro -v /etc/passwd:/etc/passwd:ro -v /etc/group:/etc/group:ro -v $BINDIR/stack:/usr/bin/stack:ro -v $STACK_DIR:$HOME/.stack -v $PANTRY_DIR:$HOME/.stack/pantry" ARGS_PREBUILD="$ARGS_COMMON -u $USERID -e HOME=$HOME -v $DOT_STACKAGE_DIR:$HOME/.stackage" ARGS_BUILD="$ARGS_COMMON" # instance-data is an undocumented feature of S3 used by amazonka, # see https://github.com/brendanhay/amazonka/issues/271 ARGS_UPLOAD="$ARGS_COMMON -u $USERID -e HOME=$HOME -v $HACKAGE_CREDS:/hackage-creds:ro -v $DOT_STACKAGE_DIR:$HOME/.stackage -v $SSH_DIR:$HOME/.ssh:ro -v $GITCONFIG:$HOME/.gitconfig:ro -e AWS_ACCESS_KEY_ID=$AWS_ACCESS_KEY_ID -e AWS_SECRET_ACCESS_KEY=$AWS_SECRET_ACCESS_KEY -v $DOT_STACKAGE_DIR:/dot-stackage" # Make sure we actually need this snapshot. We only check this for LTS releases # since, for nightlies, we'd like to run builds even if they are unnecessary to # get early warning information of upcoming failures. (See the duplicate check # below for why this is safe.) if [ $SHORTNAME = "lts" ] then docker run $ARGS_UPLOAD $IMAGE /bin/bash -c "exec curator check-target-available --target $TARGET" fi # Determine the new build plan unless NOPLAN is set # # * Update the package index (unless LTS) # * Create a new plan if [ "${NOPLAN:-}x" = "1x" ] then docker run $ARGS_PREBUILD $IMAGE /bin/bash -c "curator snapshot-incomplete --target $TARGET && curator snapshot" elif [ "${NOPLAN:-}x" = "2x" ] then docker run $ARGS_PREBUILD $IMAGE curator snapshot elif [ $SHORTNAME = "lts" ] then docker run $ARGS_PREBUILD $IMAGE /bin/bash -c "curator constraints --target $TARGET && curator snapshot-incomplete --target $TARGET && curator snapshot" else docker run $ARGS_PREBUILD $IMAGE /bin/bash -c "curator update && curator constraints --target $TARGET && curator snapshot-incomplete --target $TARGET && curator snapshot" fi # Do the rest of the pre-build actions: # # * Check that the snapshot is valid # * Fetch and unpack all needed tarballs (the build step does not have write access to the tarball directory) docker run $ARGS_PREBUILD $IMAGE /bin/bash -c 'GHCVER=$(sed -n "s/^ghc-version: \(.*\)/\1/p" constraints.yaml) && stack setup ghc-$GHCVER --verbosity=error && stack exec --resolver=ghc-$GHCVER curator check-snapshot && curator unpack' case $SHORTNAME in lts) JOBS=3 ;; nightly) JOBS=3 ;; esac if [ -e "$SHORTNAME-build.log" ] then cp -p $SHORTNAME-build.log $SHORTNAME-build.log-previous fi # Now do the actual build. We need to first set the owner of the home directory # correctly, so we run the command as root, change owner, and then use sudo to # switch back to the current user docker run $ARGS_BUILD $IMAGE nice -n 15 /bin/bash -c "chown $USER $HOME && exec sudo -E -u $USER env \"HOME=$HOME\" \"PATH=\$PATH\" curator build --jobs $JOBS" 2>&1 | tee "$SHORTNAME-build.log" # Make sure we actually need this snapshot. We used to perform this check # exclusively before building. Now we perform it after as well for the case of # nightly, where we don't perform this check beforehand. This is also slightly # safer, in case someone else already uploaded a specific snapshot while we # were building. docker run $ARGS_UPLOAD $IMAGE /bin/bash -c "exec curator check-target-available --target $TARGET" # Successful build, so we need to: # # * Upload the docs to S3 # * Upload the new snapshot .yaml file to the appropriate Github repo, also upload its constraints docker run $ARGS_UPLOAD $IMAGE /bin/bash -c "curator upload-docs --target $TARGET && curator upload-github --target $TARGET" # fixed in https://github.com/commercialhaskell/curator/pull/24 docker run $ARGS_UPLOAD $IMAGE /bin/bash -c "exec curator hackage-distro --target $TARGET" # Build and push docker image fpco/stack-build & fpco/stack-build-small for current release if [ $SHORTNAME = "lts" ] then $ROOT/dockerfiles/build.sh $TARGET $ROOT/dockerfiles/build.sh --push $TARGET $ROOT/dockerfiles/build.sh --push --small $TARGET fi echo -n "Completed at " date