Skip to content

Commit

Permalink
Added some more docs
Browse files Browse the repository at this point in the history
  • Loading branch information
Benjamin Toll committed Oct 27, 2020
1 parent bfd57cb commit 14116d3
Show file tree
Hide file tree
Showing 2 changed files with 18 additions and 2 deletions.
7 changes: 6 additions & 1 deletion scripts/release/mule/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -249,6 +249,11 @@ CHANNEL=dev VERSION=2.1.87522 mule -f package-sign.yaml package-sign
CHANNEL=dev VERSION=2.1.87522 mule -f package-upload.yaml package-upload
CHANNEL=dev VERSION=2.1.87522 NO_DEPLOY=true mule -f package-deploy.yaml package-deploy
mule -f package-deploy.yaml releases-page
docker run --name aptly-algorand --rm -i -v "$XDG_RUNTIME_DIR/gnupg/S.gpg-agent":/root/.gnupg/S.gpg-agent -v "$HOME/.gnupg/pubring.kbx":/root/.gnupg/pubring.kbx -e AWS_SECRET_ACCESS_KEY="$AWS_SECRET_ACCESS_KEY" -e AWS_ACCESS_KEY_ID="$AWS_ACCESS_KEY_ID" -e CHANNEL=dev -e REPO=algorand -e VERSION=2.1.87522 aptly-algorand bash create_and_push
docker build --build-arg AWS_SECRET_ACCESS_KEY="$AWS_SECRET_ACCESS_KEY" --build-arg AWS_ACCESS_KEY_ID="$AWS_ACCESS_KEY_ID" -t aptly-test .
docker run --name aptly-algorand --rm -i -v "$XDG_RUNTIME_DIR/gnupg/S.gpg-agent":/root/.gnupg/S.gpg-agent -v "$HOME/.gnupg/pubring.kbx":/root/.gnupg/pubring.kbx -e AWS_SECRET_ACCESS_KEY="$AWS_SECRET_ACCESS_KEY" -e AWS_ACCESS_KEY_ID="$AWS_ACCESS_KEY_ID" -e CHANNEL=dev -e REPO=algorand -e VERSION=2.1.87522 aptly-test bash create_and_push
docker run --name aptly-algorand --rm -it aptly-test
```

13 changes: 12 additions & 1 deletion scripts/release/mule/deploy/deb/create_and_push
Original file line number Diff line number Diff line change
@@ -1,5 +1,17 @@
#!/usr/bin/env bash

# This script is doing the following:
# 1. Copying the new packages from staging to the packages cache.
# 2. Syncing from the packages cache to the local container.
# 3. Aptly operations:
# i. Add all the packages to the correct $REPO. This includes the newly-synced packages.
# ii. Create the new snapshot that contains the new packages and the previous ones for
# the channel.
# iii. Switch out the old snapshot for the new one. Note that in the "publish" command that
# the $CHANNEL is the distro.
# 4. Copy the new packages from staging to `algorand-dev-deb-repo` so that the releases page can
# be generated.

CHANNEL=${CHANNEL:-stable}
REPO=${REPO:-algorand}

Expand Down Expand Up @@ -52,6 +64,5 @@ aptly repo add "$REPO" "$PKG_DIR"/*.deb
aptly snapshot create "$SNAPSHOT" from repo "$REPO"
aptly publish switch "$CHANNEL" s3:algorand-releases: "$SNAPSHOT"

# Sync with `algorand-dev-deb-repo` so the releases page can be generated.
aws s3 sync "s3://algorand-staging/releases/$CHANNEL/$VERSION" "s3://algorand-dev-deb-repo/releases/$CHANNEL/$("/root/reverse_hex_timestamp")_$VERSION"

0 comments on commit 14116d3

Please sign in to comment.