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

buildbot/lsstsw handling of anaconda is confusing

    XMLWordPrintable

    Details

    • Team:
      SQuaRE

      Description

      Buildbot sources /home/lsstsw/bin/setup.sh, which manually adds /home/lsstsw/anaconda/bin to PATH. IMO, that's confusing: we should be using EUPS any time we modify an environment variable, like PATH.

      However, the real problem is that buildbot also tags whatever version of anaconda is current with the buildbot run's tag with the buildbot run's bXXX tag (I think; until I declared anaconda 2.1.0 today, there was only one declared version of anaconda, so I'm not sure if the current tag played a role). In any case, buildbot was certainly declaring an anaconda version other than the one it was using with the buildbot run's tag.

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          Hide
          Permalink
          frossie Frossie Economou added a comment -

          Mario/KT - would you like to recommend a way forward here?

          Show
          frossie Frossie Economou added a comment - Mario/KT - would you like to recommend a way forward here?
          Hide
          Permalink
          ktl Kian-Tat Lim added a comment -

          Build, distribute, and install anaconda 2.1.0 as part of the stack. Should have been done as soon as we switched lsstsw.

          Show
          ktl Kian-Tat Lim added a comment - Build, distribute, and install anaconda 2.1.0 as part of the stack. Should have been done as soon as we switched lsstsw.
          Hide
          Permalink
          mjuric Mario Juric added a comment -

          Kian-Tat Lim that will work (though I'm still unhappy we upgraded Anaconda for no compelling reason, thus needlessly breaking compatibility, etc.).

          Going forward, I think the right thing to do is to make lsstsw's Anaconda managed by EUPS.

          Show
          mjuric Mario Juric added a comment - Kian-Tat Lim that will work (though I'm still unhappy we upgraded Anaconda for no compelling reason, thus needlessly breaking compatibility, etc.). Going forward, I think the right thing to do is to make lsstsw's Anaconda managed by EUPS.
          Hide
          Permalink
          jbosch Jim Bosch added a comment -

          By the way, the same should be done with git: lsstsw installs git 1.9.0 manually, but installs and declares git 1.8.5.2 via eups.

          Show
          jbosch Jim Bosch added a comment - By the way, the same should be done with git: lsstsw installs git 1.9.0 manually, but installs and declares git 1.8.5.2 via eups.
          Hide
          Permalink
          jhoblitt Joshua Hoblitt added a comment -

          I'm changing the status of this issue to invalid since I don't believe it's relevant any more

          Show
          jhoblitt Joshua Hoblitt added a comment - I'm changing the status of this issue to invalid since I don't believe it's relevant any more

            People

            Assignee:
            frossie Frossie Economou
            Reporter:
            jbosch Jim Bosch
            Watchers:
            Frossie Economou, Jim Bosch, Joshua Hoblitt, Kian-Tat Lim, Mario Juric
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Jenkins

                No builds found.