| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Bumped version used in release script (documentation) | Sven Gothel | 2023-02-01 | 1 | -2/+2 |
| | | |||||
| * | jenkins-builds/promote-to-release-ssh-git.sh: Maven required the plain ↵ | Sven Gothel | 2023-02-01 | 1 | -2/+3 |
| | | | | | version w/ leading 'v' | ||||
| * | jenkins-builds/promote-to-release-ssh-git.sh: Add version to logfile name | Sven Gothel | 2023-02-01 | 1 | -1/+1 |
| | | |||||
| * | jenkins-builds/promote-to-release-ssh-git.sh: Add the maven ↵ | Sven Gothel | 2023-02-01 | 1 | -2/+15 |
| | | | | | make-all-jogamp.sh deployment step and log to file; Drop ssh-scp variant. | ||||
| * | New release script: promote-to-release.sh | Sven Gothel | 2020-01-05 | 1 | -0/+24 |
| 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 | |||||
 |
index : jogamp-scripting.git | |
| JogAmp related scripts repository |
| summaryrefslogtreecommitdiffstats |