Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: Continuous Integration
-
Labels:
-
Story Points:1
-
Epic Link:
-
Team:SQuaRE
Description
The sims team would like an automatically built weekly sims version that is built on the weekly build of lsst_distrib. They would like the result to be a binary distribution that would allow end users to install a full stack of sims plus DM dependencies that are all consistent with the weekly build. I.e.
$> eups distrib install lsst_sims -t w_2018_13
|
This is currently possible to do by hand, but it would be useful to them to have it automatically build. They are very clear that a failing lsst_sims weekly build should not imply a failing lsst_distrib build.
Attachments
Activity
lsst_sims should be stable now
Sorry about the delay.
A new job named sims/weekly-release https://ci.lsst.codes/blue/organizations/jenkins/sims%2Fweekly-release/activity has been created. Which will be triggered at the end of the release/weekly-release job in a fire-and-forget (aka "no wait") manner, which ensures that it will only be triggered after the scipipe weekly release is published while its build status won't effect the upstream job.
A test build on top of w_2018_34 (without osx tarballs) has succesful and has been published as sims_w_2018_34. Future published eups packages will use the tag format sims_<scipipe weekly release>.
I'm put this ticket into self review to follow up next week that the build is correctly triggered by the scipipe weekly.
The sims weekly builds appear to be triggering as expected.
`sncosmo` is broken on master, preventing further dev work at this time: https://ci.lsst.codes/blue/organizations/jenkins/stack-os-matrix/detail/stack-os-matrix/28500/pipeline