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

Migrate lsst/ci_hsc repo to git-lfs.lsst.codes

    XMLWordPrintable

    Details

      Description

      The github lfs backed repo https://github.com/lsst/ci_hsc needs to be migrated to git-lfs.lsst.codes. A sanity check for any other "live" lfs repos under the lsst github org might also be a good idea.

        Attachments

          Issue Links

            Activity

            Hide
            jmatt J Matt Peterson [X] (Inactive) added a comment -

            The new repository is in the same location:

            https://github.com/lsst/ci_hsc

            The old repository is still temporarily available here:

            https://github.com/lsst/ci_hsc_old

            I'll remove the old repository soon. I just didn't want to destroy it until this was reviewed.

            Note: I created a new repository. Renamed the original repository to ci_hsc_old. Then renamed the new repository to ci_hsc. This is because the git-lfs client can't easily purge data in it's storage backend. So the best way to ensure we stop using GitHub's git-lfs is to simply delete the repository entirely and mirror into a new repository.

            Show
            jmatt J Matt Peterson [X] (Inactive) added a comment - The new repository is in the same location: https://github.com/lsst/ci_hsc The old repository is still temporarily available here: https://github.com/lsst/ci_hsc_old I'll remove the old repository soon. I just didn't want to destroy it until this was reviewed. Note: I created a new repository. Renamed the original repository to ci_hsc_old. Then renamed the new repository to ci_hsc. This is because the git-lfs client can't easily purge data in it's storage backend. So the best way to ensure we stop using GitHub's git-lfs is to simply delete the repository entirely and mirror into a new repository.
            Hide
            jmatt J Matt Peterson [X] (Inactive) added a comment -

            See comments.

            The new repository has the same name but uses git-lfs. Users may need to re-clone? I don't have a pre and post git clone to test if the repository is still stable after my changes. But I can say that it works if you have git-lfs installed, configured and clone it.

            Show
            jmatt J Matt Peterson [X] (Inactive) added a comment - See comments. The new repository has the same name but uses git-lfs. Users may need to re-clone? I don't have a pre and post git clone to test if the repository is still stable after my changes. But I can say that it works if you have git-lfs installed, configured and clone it.
            Hide
            tjenness Tim Jenness added a comment -

            I think you may want to ask Paul Price to review this. He cares deeply about whether the content matches and will probably want to run the HSC integration test on this repository before it is approved.

            Show
            tjenness Tim Jenness added a comment - I think you may want to ask Paul Price to review this. He cares deeply about whether the content matches and will probably want to run the HSC integration test on this repository before it is approved.
            Hide
            jmatt J Matt Peterson [X] (Inactive) added a comment -

            Adding Paul Price at Tim Jenness suggestion.

            Show
            jmatt J Matt Peterson [X] (Inactive) added a comment - Adding Paul Price at Tim Jenness suggestion.
            Hide
            jmatt J Matt Peterson [X] (Inactive) added a comment -

            I moved the lfs configuration file (.gitconfig) to the first commit. So the git history has been rewritten.

            Show
            jmatt J Matt Peterson [X] (Inactive) added a comment - I moved the lfs configuration file (.gitconfig) to the first commit. So the git history has been rewritten.
            Hide
            price Paul Price added a comment -

            First problem is that there doesn't appear any easy method for installing git-lfs as an unprivileged user. All installation instructions for git-lfs appear to involve building a .deb or .rpm, but I want to install it into my own user version of /usr/local.

            Show
            price Paul Price added a comment - First problem is that there doesn't appear any easy method for installing git-lfs as an unprivileged user. All installation instructions for git-lfs appear to involve building a .deb or .rpm, but I want to install it into my own user version of /usr/local .
            Hide
            jhoblitt Joshua Hoblitt added a comment -

            Paul Price Are you up and running now?

            Show
            jhoblitt Joshua Hoblitt added a comment - Paul Price Are you up and running now?

              People

              Assignee:
              jmatt J Matt Peterson [X] (Inactive)
              Reporter:
              jhoblitt Joshua Hoblitt
              Reviewers:
              Joshua Hoblitt, Paul Price
              Watchers:
              Frossie Economou, J Matt Peterson [X] (Inactive), John Swinbank, Joshua Hoblitt, Paul Price, Tim Jenness
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.