summaryrefslogtreecommitdiffstats
path: root/jenkins-builds/promote-to-release.sh
Commit message (Collapse)AuthorAgeFilesLines
* promote-to-release: Also update the 'jogamp-next' symbolic linkSven Gothel2020-01-061-1/+4
|
* New release script: promote-to-release.shSven Gothel2020-01-051-0/+84
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