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

Implement pinning of Firefly version in suit repo

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: SUIT
    • Labels:
      None
    • Story Points:
      2
    • Epic Link:
    • Sprint:
      SUIT Sprint 2019-08, SUIT Sprint 2019-09
    • Team:
      Science User Interface

      Description

      Per today's discussion, this ticket asks that the suit package be modified to include a script that encapsulates the full build process for that package, including its dependency on an explicitly specified version of Caltech-IPAC/firefly.

      (The equivalent of this already exists in the IPAC Jenkins scripts repo for Firefly/suit builds, so the task here is just to ensure that that information is in the suit repo itself, to facilitate LSST-driven builds of the package.)

      The Firefly version may be specified in the script itself or in a supporting data file. Gregory Dubois-Felsmann has a mild preference for the latter, decoupling the build logic from the version numbering.

      This is a high-priority task as we wish to converge with LSST on an LSST-maintainable build process by the end of FY19.

        Attachments

          Issue Links

            Activity

            No work has yet been logged on this issue.

              People

              Assignee:
              loi Loi Ly
              Reporter:
              gpdf Gregory Dubois-Felsmann
              Reviewers:
              Gregory Dubois-Felsmann
              Watchers:
              Gabriele Comoretto [X] (Inactive), Gregory Dubois-Felsmann, Xiuqin Wu [X] (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.