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

Implement RFC-802, add analysis_drp to lsst_distrib

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Story Points:
      2
    • Epic Link:
    • Sprint:
      DRP S21b, DRP S22A
    • Team:
      Data Release Production
    • Urgent?:
      No

      Description

      Add analysis_drp to lsst_distrib.

        Attachments

          Issue Links

            Activity

            Hide
            jbosch Jim Bosch added a comment -

            I'm marking this as a blocker of DM-33034, because that ticket will require that all tasks referenced by pipelines in drp_pipe (which is itself still pending on DM-30891) be importable once drp_pipe is setup, and as one of those pipelines references analysis_drp, we'll need to make drp_pipe depend on analysis_drp at that point. It'd be nice if analysis_drp was included in lsst_distrib directly before we add it indirectly as a dependency of drp_pipe.

            Show
            jbosch Jim Bosch added a comment - I'm marking this as a blocker of DM-33034 , because that ticket will require that all tasks referenced by pipelines in drp_pipe (which is itself still pending on DM-30891 ) be importable once drp_pipe is setup, and as one of those pipelines references analysis_drp , we'll need to make drp_pipe depend on analysis_drp at that point. It'd be nice if analysis_drp was included in lsst_distrib directly before we add it indirectly as a dependency of drp_pipe .
            Hide
            sophiereed Sophie Reed added a comment -

            If you could review this for me I would be very grateful.

            Show
            sophiereed Sophie Reed added a comment - If you could review this for me I would be very grateful.
            Hide
            csaunder Clare Saunders added a comment -

            I just took a preliminary look at this--do you have a pull request on lsst/repos/etc/repos.yaml to go with this, or are you going to do that later? That is the main thing that you need to add the package to lsst_distrib unless this is going to be a dependency of other packages.

            Show
            csaunder Clare Saunders added a comment - I just took a preliminary look at this--do you have a pull request on lsst/repos/etc/repos.yaml to go with this, or are you going to do that later? That is the main thing that you need to add the package to lsst_distrib unless this is going to be a dependency of other packages.
            Hide
            sophiereed Sophie Reed added a comment -

            I do, sorry I forgot to push it! Should be done now.

            Show
            sophiereed Sophie Reed added a comment - I do, sorry I forgot to push it! Should be done now.
            Hide
            csaunder Clare Saunders added a comment -

            This looks good to me, except you need a one character change in lsst/repos. I think that if you add the ticket branch for analysis_drp in repos.yaml you should be able to test whether you have successfully added the package in Jenkins.

            Show
            csaunder Clare Saunders added a comment - This looks good to me, except you need a one character change in lsst/repos . I think that if you add the ticket branch for analysis_drp in repos.yaml you should be able to test whether you have successfully added the package in Jenkins.

              People

              Assignee:
              sophiereed Sophie Reed
              Reporter:
              sophiereed Sophie Reed
              Reviewers:
              Clare Saunders
              Watchers:
              Clare Saunders, Jim Bosch, Sophie Reed, Yusra AlSayyad
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.