Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-11549

generate "nightly" releases


    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: Continuous Integration
    • Labels:


      There are frequently breakages / regressions that occur in the normal course of development between runs of weekly-release, which for various reason only turn up during the weekly release cycle, and these problems are preventing its on time production. As the "weekly" is now on the critical path for many developers, this results in unplanned / reactive ops works nearly every week.

      In hopes of beating down the rate of failure, a more limited per day or "nightly" release is proposed. At least initially, this would treated as a shake down or quasi-canary build and not considered as an "official" product.

      The "nightly" would differ from the weekly in the following ways:

      • no git tag (initially) – a moving "nightly" tag might be useful at some point while avoiding having to eventually prune git tags
      • only a single eups distrib tag would be created
      • tarballs limited to py3 (reducing runtime / cpu consumption by half)
      • no docker images (initially – this will also reduce resource consumption)
      • eups distrib tag format would be d_<year><mon><day>. Where the d prefix is for "day" and year/mon/day would be the Gregorian calendar date in project standard time.


          Issue Links



              • Assignee:
                jhoblitt Joshua Hoblitt
                jhoblitt Joshua Hoblitt
                Fritz Mueller, Frossie Economou, John Swinbank, Joshua Hoblitt, Kian-Tat Lim, Simon Krughoff, Tim Jenness
              • Votes:
                0 Vote for this issue
                7 Start watching this issue


                • Created:

                  Summary Panel