Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: Continuous Integration, Developer Infrastructure
-
Labels:None
-
Story Points:15
-
Epic Link:
-
Team:SQuaRE
Description
Produced tarballs are to copied to a versioned s3 bucket, which will serve as the canonical repository.
Attachments
Issue Links
- blocks
-
DM-9526 add tarball production to weekly tag/release jenkins' job
- Done
- is blocked by
-
DM-9523 update lsstsw/newinstall EUPS version
- Done
-
DM-9527 setup new EUPS_PKGROOT(s) for OSX/linux tarballs
- Done
- is triggering
-
DM-9806 update lsstsw/newinstall to EUPS 2.1.2
- Done
- relates to
-
DM-9223 add "newinstall.sh" canary build to weekly-release
- Done
There was some scope creep on this task to also start pushing the eupspkg packages and doxygen builds to s3, as this was a small amount of additional work over setting up s3 pushes / hosted for the tarball packages.
https://eups.lsst.codes will be the production host for eupspkg/tarball packages while http://doxygen.lsst.codes (note this is non-https) will host doxygen builds. Both of these new sites are live but large file syncs are still in progress (and likely will be for several days for the historical doxygen builds).