summaryrefslogtreecommitdiffstats
path: root/jenkins-builds/promote-latest-builds.sh
diff options
context:
space:
mode:
authorSven Gothel <[email protected]>2020-01-05 00:52:45 +0100
committerSven Gothel <[email protected]>2020-01-05 00:52:45 +0100
commit91db9a7221db6d5af963da2b586c4875c19d048b (patch)
tree761f4537fc3d826f2ce63e857c61ae4c1666c359 /jenkins-builds/promote-latest-builds.sh
parent8e1e55d13b3cbd5a2744314b7285171a8a3ecd2f (diff)
New release script: promote-to-release.sh
This is essentially a simplified variant as it only copies the aggregated folder and creates the symbolic link in the deployment root dir. The remote shell commands kicking-off release promotion on the server from our home-machine, jenkins-builds/promote-to-release-ssh-*.sh do pull the resulting sha512sum.txt, gpg-sign it and push the sha512sum.txt.sig back to the server. This allows full data integretiy over all aggregrated files having their sha512 stored in the sha512sum.txt
Diffstat (limited to 'jenkins-builds/promote-latest-builds.sh')
0 files changed, 0 insertions, 0 deletions