Created mule tasks for aptly, releases page and docker hub images

[btoll]

Summary

I decided to make mule tasks for generating the releases page and creating/pushing the docker image(s) to docker hub.

The only thing that hasn't been mule-fied is the deb deployment. To do that, do the following steps:

• cd to the deploy/deb directory

• build the image:

   docker build --build-arg AWS_ACCESS_KEY_ID="$AWS_ACCESS_KEY_ID" --build-arg AWS_SECRET_ACCESS_KEY="$AWS_SECRET_ACCESS_KEY" -t aptly-algorand .
  

• run the container:

   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=stable -e REPO=algorand -e VERSION=2.1.6 aptly-algorand bash create_and_push
  

Note that the releases_page directory is just temporary. It was easiest to add the files here to create the generate releases page mule task instead of futzing with tokens or another way to access a private github repository. This will be removed in the near future as we move to a better plan.

For all subsequent deployments, simply run the container and pass it the S3_SOURCE, VERSION and CHANNEL.

Test Plan

mule -f package.yaml package
CHANNEL=dev VERSION=2.1.87522 SHA=730b3fd0 mule -f package-test.yaml package-test
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

[egieseke]

A few questions.

[egieseke]

Was the use of ARCH_BIT removed?

[btoll]

I'll remove, good catch.

[btoll]

Oh, wait, that's on a different PR, haha.

So, yes, all those will be removed when that is merged.

[egieseke]

Is this still accurate for the Jenkins pipeline?

[btoll]

Yes

The base branch was changed.

[egieseke]

Looks good.