Build release job#698
Conversation
Also, renamed files {build_,}release.sh and {build_,}setup.sh
-%_gpg_name Algorand RPM <rpm@algorand.com> +%_gpg_name rpm algorand <rpm@algorand.com>
Moved `Jenkinsfile` into controller/ subdir.
|
|
||
| cat <<EOF>"${HOME}/.rpmmacros" | ||
| %_gpg_name Algorand RPM <rpm@algorand.com> | ||
| %_gpg_name ALGORAND RPM <rpm@algorand.com> |
There was a problem hiding this comment.
pretty sure the real key's username isn't all caps
There was a problem hiding this comment.
Oh, I just saw that's in archive. I'm going to remove that directory as soon as this has settled. I probably shouldn't have versioned that!
| trap "rm -rf ${RPMTMP}" 0 | ||
| scripts/build_rpm.sh ${RPMTMP} | ||
| cp -p ${RPMTMP}/*/*.rpm /root/subhome/node_pkg | ||
| trap 'rm -rf ${RPMTMP}' 0 |
There was a problem hiding this comment.
this should be doublequote so that $RPMTMP is substituted in
|
|
||
| set -e | ||
| set -x | ||
| #set -ex |
There was a problem hiding this comment.
I will, I want to make sure I'm not getting any false positives while I'm still running builds. I should've left a comment explaining that.
| #https://releases.algorand.com/key.pub | ||
| #gpgkeys: protocol `https' not supported | ||
|
|
||
| curl -o /root/stuff/key.pub https://releases.algorand.com/key.pub |
There was a problem hiding this comment.
pretty sure at this stage we want to test with the fake key, not the real key from releases; or did this test move to later in the flow after signing the real thing?
| if [ -z "${APTLY_S3_NAME}" ]; then | ||
| APTLY_S3_NAME=algorand-releases | ||
| fi | ||
| #if [ -z "${APTLY_S3_NAME}" ]; then |
There was a problem hiding this comment.
the point of this if is that you can override the default
There was a problem hiding this comment.
Actual APT .deb package serving happens from algorand-releases bucket, so that would be correct.
1e479d6 to
f0c2072
Compare
b8b78b8 to
0c71821
Compare
tsachiherman
left a comment
There was a problem hiding this comment.
looks like a good milestone.
algobolson
left a comment
There was a problem hiding this comment.
I see this was merged with unsettled issues. We should expect a couple days build time the first time we try to release using these scripts.
| export DEFAULTNETWORK | ||
| export PKG_ROOT=${HOME}/node_pkg | ||
| export VARIATIONS="base" | ||
| # tell underlying 'build' scripts we already built |
There was a problem hiding this comment.
this comment was meant to go with export NO_BUILD=true
| gpg -u "${SIGNING_KEY_ADDR}" --clearsign "${HASHFILE}" | ||
|
|
||
| cp -p "${REPO_ROOT}/installer/rpm/algorand.repo" "${HOME}/prodrepo/algorand.repo" | ||
|
|
There was a problem hiding this comment.
it looks like we lost the functionality of sign_centos_docker.sh to do the final signing of the release rpms and prodrepo
This is my original feature branch. I've been working off of this again because I was getting odd linker errors when go was building on the other branch (you can see this here #690).
Rather than go down a rabbit hole, I merged what I needed back into this feature branch and kept moving.
Please see the README for details.