Provide 0.12.2 upgrade boxes #4393
Conversation
Things got shifted a bit in the release story, now we have a bucket that exists at dev-bin.ops.securedrop.org. These files should be placed here under the /vagrant/ key.
Since our buckets are behind cloudfront and AWS is not smart enough to generate it's own index files - let's create them on-the-fly during upload time. This will be visible at: https://dev-bin.ops.securedrop.org/vagrant/
emkll
force-pushed
the
1824_PortSDUpgradeBoxStorage
branch
from
f18d7c5 to
581efc2
Compare
|
@msheiny is already working on pushing up the historical images to the new bucket. Once that's done, let's update the all the URLs in the JSON files to use the new bucket, then we should be ready for final review. |
|
Thanks for updating the links @msheiny ! This should be now ready for review. |
|
Confirmed most of the test plan so far, still need to run the Trusty steps just to be sure. Will circle back on that tomorrow. |
The Trusty boxes pulled successfully. Given that building Trusty packages no longer works, due to dependency changes in #4297, the |
Status
Work in progress : we need to finish uploading historical boxes to the new s3 bucket and update URLs in this PR
Description of Changes
Closes #4338, closes #4329.
Changes proposed in this pull request:
Testing
make build-debsmake upgrade-startpulls in the newly-built 0.12.2 box (see Source Interface)make upgrade-test-localupgrades the box to 0.13.0~rc1 without error (see Source Interface)make upgrade-trusty-startpulls in the newly-built 0.12.2 box (see Source Interface)Deployment
Developer environment only
Checklist
If you made non-trivial code changes: