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

Changes to lsstsw to add ctrl_platform_lsstvc remove old ctrl_platform_* references

    XMLWordPrintable

    Details

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

      Description

      This work removes the following:

      ctrl_platform_lsst
      ctrl_platform_gordon

      from etc/repos.yaml

      adds:

      ctrl_platform_lsstvc

      to etc/repos.yaml

      and moves the repos to

      lsst-dm/legacy_ctrl_platform_lsst
      lsst-dm/legacy_ctrl_platform_gordon

        Attachments

          Issue Links

            Activity

            Hide
            spietrowicz Steve Pietrowicz added a comment -

            Changing the file repos.yaml in lsstsw
            changing the ups/lsst_distrib.table file

            Show
            spietrowicz Steve Pietrowicz added a comment - Changing the file repos.yaml in lsstsw changing the ups/lsst_distrib.table file
            Hide
            spietrowicz Steve Pietrowicz added a comment -

            Since we've been talking about this, can you take a quick look at the pull request for this ticket?
            It's just removing two packages, and adding one.
            This has been tested on a Jenkins build and builds against py2.

            Show
            spietrowicz Steve Pietrowicz added a comment - Since we've been talking about this, can you take a quick look at the pull request for this ticket? It's just removing two packages, and adding one. This has been tested on a Jenkins build and builds against py2.
            Hide
            tjenness Tim Jenness added a comment -

            Please don't remove packages from repos.yaml. That can lead to people being unable to build older versions of lsst_distrib. Update the URLs for those entries to point to the new location.

            Show
            tjenness Tim Jenness added a comment - Please don't remove packages from repos.yaml. That can lead to people being unable to build older versions of lsst_distrib. Update the URLs for those entries to point to the new location.
            Hide
            spietrowicz Steve Pietrowicz added a comment -

            just so I'm clear, to be sure I'm doing this in the proper order, and fix the merge that shouldn't have done I should:

            1) move lsst/ctrl_platform_gordon to lsst-dm/legacy_ctrl_platform_gordon
            2) move lsst/ctrl_platform_lsst to lsst-dm/legacy_ctrl_platform_lsst
            3) create a new branch for lsst/lsstsw (something like: tickets/DM-8667a)
            4) add the following to lsst/lsstsw/etc/repos.yaml:

            ctrl_platform_lsst: https://github.com/lsst-dm/legacy_ctrl_platform_lsst.git
            ctrl_platform_gordon: https://github.com/lsst-dm/legacy_ctrl_platform_gordon.git

            5) to a pull to trigger the PR and wait for it to go green
            6) On GitHub, hit merge for lsstsw
            7) merge the lsst/lsst_distrib branch tickets/DM-8667 with the two old packages removed, and the new package added.

            Does that look right to you?

            Show
            spietrowicz Steve Pietrowicz added a comment - just so I'm clear, to be sure I'm doing this in the proper order, and fix the merge that shouldn't have done I should: 1) move lsst/ctrl_platform_gordon to lsst-dm/legacy_ctrl_platform_gordon 2) move lsst/ctrl_platform_lsst to lsst-dm/legacy_ctrl_platform_lsst 3) create a new branch for lsst/lsstsw (something like: tickets/ DM-8667 a) 4) add the following to lsst/lsstsw/etc/repos.yaml: ctrl_platform_lsst: https://github.com/lsst-dm/legacy_ctrl_platform_lsst.git ctrl_platform_gordon: https://github.com/lsst-dm/legacy_ctrl_platform_gordon.git 5) to a pull to trigger the PR and wait for it to go green 6) On GitHub, hit merge for lsstsw 7) merge the lsst/lsst_distrib branch tickets/ DM-8667 with the two old packages removed, and the new package added. Does that look right to you?
            Hide
            tjenness Tim Jenness added a comment -

            Perfect. And the reason this doesn't break Jenkins in the time between you moving the repo and changing repos.yaml is because Github handles redirects if a repo is moved.

            Show
            tjenness Tim Jenness added a comment - Perfect. And the reason this doesn't break Jenkins in the time between you moving the repo and changing repos.yaml is because Github handles redirects if a repo is moved.
            Hide
            spietrowicz Steve Pietrowicz added a comment -

            I was wondering about that time gap. Thanks!

            Show
            spietrowicz Steve Pietrowicz added a comment - I was wondering about that time gap. Thanks!
            Hide
            spietrowicz Steve Pietrowicz added a comment -

            This work has been completed

            Show
            spietrowicz Steve Pietrowicz added a comment - This work has been completed

              People

              Assignee:
              spietrowicz Steve Pietrowicz
              Reporter:
              spietrowicz Steve Pietrowicz
              Reviewers:
              Tim Jenness
              Watchers:
              Steve Pietrowicz, Tim Jenness
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.