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

Update shared stack build to take account of newinstall changes

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Story Points:
      2
    • Sprint:
      DRP F17-3, DRP F17-4
    • Team:
      Data Release Production

      Description

      Recent changes to newinstall.sh (e.g. on DM-9526, etc) have substantially changed the way it works so that it's no longer compatible with shared-stack.py. Update the latter.

      In particular, we'll need to:

      • Customize the environment so it aligns with that provided by newinstall.sh;
      • Rework the installation procedure so that it provides something equivalent to newinstall.sh.

        Attachments

          Issue Links

            Activity

            Hide
            pschella Pim Schellart [X] (Inactive) added a comment -

            Does this include binary installs?

            Show
            pschella Pim Schellart [X] (Inactive) added a comment - Does this include binary installs?
            Hide
            swinbank John Swinbank added a comment -

            No.

            Well, rather: not necessarily. The binary installs should effectively be a drop-in replacement for building from source. If it follows the structure set up by newinstall.sh, the stack should be basically agnostic as to whether it's using binaries or source.

            Given that the build environment is quite straightforward and well tested (ie, we're not really gaining in robustness from using binaries) and that performance isn't an issue, I wasn't intending to make use of binaries on this ticket just for simplicity.

            Show
            swinbank John Swinbank added a comment - No. Well, rather: not necessarily. The binary installs should effectively be a drop-in replacement for building from source. If it follows the structure set up by newinstall.sh , the stack should be basically agnostic as to whether it's using binaries or source. Given that the build environment is quite straightforward and well tested (ie, we're not really gaining in robustness from using binaries) and that performance isn't an issue, I wasn't intending to make use of binaries on this ticket just for simplicity.

              People

              • Assignee:
                swinbank John Swinbank
                Reporter:
                swinbank John Swinbank
                Watchers:
                John Swinbank, Pim Schellart [X] (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Summary Panel