You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tried to do it before I finished, but the 'chown -R' command outlined below needs sudo access for the Jenkins user and I figured that's not worth my mucking around.
This will be in the Release notes, but these are the things that would be good for Jenkins to do automatically. Until then, they will be done manually:
Symlink download/75/ to ‘current’ (rm current; ln -s 75/ current)
Archive ‘release_current’ as 75_release_current_final.sql.gz , storing it on s3 using aws s3 cp 75_release_current_final_sql.gz s3://reactome/private/releases/75/
Archive 'release_current' as test_reactome_${releaseVersion}.sql.gz, storing it on S3 using aws s3 cp test_reactome_75.sql.gz s3://reactome/private/databases/release/final/
Do an equivalent of UpdateGKCurrent: update the 'current' database on Release using either of the 'release_final' databases created
Email developers list saying that it is ready for review
I'll also be adding all these steps to the Release document so that they still get completed
The text was updated successfully, but these errors were encountered:
Tried to do it before I finished, but the 'chown -R' command outlined below needs sudo access for the Jenkins user and I figured that's not worth my mucking around.
This will be in the Release notes, but these are the things that would be good for Jenkins to do automatically. Until then, they will be done manually:
releaseVersion = 75
previousReleaseVersion = 74
(eg. rm -r 74/)
(chown -R www-data:reactome 75/)
(tar -zcf 75-download.tgz 75/; aws s3 cp 75-download.tgz s3://reactome/private/releases/75/)
aws s3 cp 75_release_current_final_sql.gz s3://reactome/private/releases/75/
test_reactome_${releaseVersion}.sql.gz
, storing it on S3 usingaws s3 cp test_reactome_75.sql.gz s3://reactome/private/databases/release/final/
UpdateGKCurrent
: update the 'current' database on Release using either of the 'release_final' databases createdI'll also be adding all these steps to the Release document so that they still get completed
The text was updated successfully, but these errors were encountered: