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

unable to build release git tag when 3rd party deps change

    Details

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

      Description

      The fundamental issue is that lsstsw/lsst-build operate on refs in the git repo. Due to the way eups generates version strings from git tags, we are unable to tag the repos for 3rd party products. This means that we are unable to build a last tagged release from source once a 3rd party dependency has been upgraded to an incompatible version.

        Attachments

          Issue Links

            Activity

            Hide
            jhoblitt Joshua Hoblitt added a comment -

            As a minimally invasive work around, support has been added to the jenkins run-rebuild job for uploading an override repos.yaml. This is functional but will likely become painful over time as repos are moved/renamed. If this feature receives much usage, a better solution would be to modify lsst-build to allow a separate "refs.yaml" file that may be layered on top of a repos.yaml.

            Example repos.yaml for building the 12.1 tagged release:

            https://gist.github.com/jhoblitt/c8564653432ff8c072c2ebab7c128446

            Show
            jhoblitt Joshua Hoblitt added a comment - As a minimally invasive work around, support has been added to the jenkins run-rebuild job for uploading an override repos.yaml . This is functional but will likely become painful over time as repos are moved/renamed. If this feature receives much usage, a better solution would be to modify lsst-build to allow a separate " refs.yaml " file that may be layered on top of a repos.yaml . Example repos.yaml for building the 12.1 tagged release: https://gist.github.com/jhoblitt/c8564653432ff8c072c2ebab7c128446
            Hide
            tjenness Tim Jenness added a comment -

            I think you could add a thirdparty-12.1 tag to the thirdparties and include that in the rebuild command along with 12.1. It's the tags starting with numbers that are special.

            Show
            tjenness Tim Jenness added a comment - I think you could add a thirdparty-12.1 tag to the thirdparties and include that in the rebuild command along with 12.1 . It's the tags starting with numbers that are special.

              People

              • Assignee:
                jhoblitt Joshua Hoblitt
                Reporter:
                jhoblitt Joshua Hoblitt
                Watchers:
                Frossie Economou, J Matt Peterson [X] (Inactive), Joshua Hoblitt, Tim Jenness
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Summary Panel