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

Add option to deploy rubin-env-developer in lsstsw

    XMLWordPrintable

    Details

    • Type: Story
    • Status: To Do
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: lsstsw
    • Labels:
      None
    • Team:
      Architecture
    • Urgent?:
      No

      Description

      Once rubin-env-developer is available, lsstsw should be able to use it. I would be inclined to make it the default environment rather than requiring a command line flag to enable it. Most users of lsstsw are already developers.

        Attachments

          Issue Links

          is blocked by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-35915 Add rubin-env-developer to conda-forge

          • Done
          is triggered by

          RFC - An issue whose primary purpose is to advertise an intent and allow stakeholders to comment. RFC-869 Add rubin-env-developer conda-forge variant

          • Implemented

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            ktl Kian-Tat Lim added a comment -

            It's possible that most lsstsw uses are Jenkins-related, where we probably don't want -developer.

            Show
            ktl Kian-Tat Lim added a comment - It's possible that most lsstsw uses are Jenkins-related, where we probably don't want -developer .
            Hide
            Permalink
            tjenness Tim Jenness added a comment -

            No idea but I use lsstsw all the time. Am I the only person?

            Show
            tjenness Tim Jenness added a comment - No idea but I use lsstsw all the time. Am I the only person?
            Hide
            Permalink
            tjenness Tim Jenness added a comment -

            It's probably fine if I mamba install the developer env manually after deployment – at least I know that it will solve.

            Show
            tjenness Tim Jenness added a comment - It's probably fine if I mamba install the developer env manually after deployment – at least I know that it will solve.

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              tjenness Tim Jenness
              Watchers:
              Kian-Tat Lim, Tim Jenness
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:

                  Jenkins

                  No builds found.