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

Create a permanent and accessible mapping of the BB# and the bNNN.

    Details

    • Story Points:
      2
    • Team:
      SQuaRE

      Description

      Create a permanent and accessible mapping of the BB# and the bNNN.

      The users are interested in the BB# since is is used to point to the STDIO file form the entire stack build.
      The bNNN is needed because the daily life of the developer revolves around the stack tagged alternately by the bNNN tags and/or the DM Release tags.

        Attachments

          Activity

          Hide
          robyn Robyn Allsman [X] (Inactive) added a comment -

          A simple text based file was created on the lsst cluster at: "~lsstsw/build/eupsTag_buildbotNum".

          • The content is: <eups-tag>:<buildbot-buildNumber>:<exit status of build>:<branches used in build>.
          • An example for a successful build is:

          A successful build is one in which all packages for the buildbot run's product have been built and unit tested successfully. Currently that includes all of sims, qserv and lsst_distrib packages and their dependencies. In the future, the builds will be dedicated to one of

          {lsst_distrib, sims, qserv}

          and the associated concordance files will be likewise specialized.

          The Continuous integration (CI) software allocates an eups-tag at the start of a build. If that build fails, it still generates an entry in: "~lsstsw/build/eupsTag_buildbotNum", for example: "b202:433:failure:master".

          It is important to note that the CI software recognizes a later build as requiring the same set of package/version for all build products in the run. If that is the case, it assigns the same eups-tag and proceeds with the build. Note that the buildbot-buildNumber will be different since buildbot assigns a new buildNumber for every buildbot build.

          A common situation is a series of <same eups-tag>:<diff buildbot-buildNumber>:failure:<same branches> followed by a final: <same eups-tag>:<diff buildbot-buildNumber>:success:<same branches>. This indicates it took a couple of tries to clean up the <branches> code in successively higher-level packages culminating in a clean build from start to finish.

          This info needs to get integrated into the confluence document: https://confluence.lsstcorp.org/display/LDMDG/Triggering+a+Buildbot+Build

          Show
          robyn Robyn Allsman [X] (Inactive) added a comment - A simple text based file was created on the lsst cluster at: "~lsstsw/build/eupsTag_buildbotNum". The content is: <eups-tag>:<buildbot-buildNumber>:<exit status of build>:<branches used in build>. An example for a successful build is: A successful build is one in which all packages for the buildbot run's product have been built and unit tested successfully. Currently that includes all of sims, qserv and lsst_distrib packages and their dependencies. In the future, the builds will be dedicated to one of {lsst_distrib, sims, qserv} and the associated concordance files will be likewise specialized. The Continuous integration (CI) software allocates an eups-tag at the start of a build. If that build fails, it still generates an entry in: "~lsstsw/build/eupsTag_buildbotNum", for example: "b202:433:failure:master". It is important to note that the CI software recognizes a later build as requiring the same set of package/version for all build products in the run. If that is the case, it assigns the same eups-tag and proceeds with the build. Note that the buildbot-buildNumber will be different since buildbot assigns a new buildNumber for every buildbot build. A common situation is a series of <same eups-tag>:<diff buildbot-buildNumber>:failure:<same branches> followed by a final: <same eups-tag>:<diff buildbot-buildNumber>:success:<same branches>. This indicates it took a couple of tries to clean up the <branches> code in successively higher-level packages culminating in a clean build from start to finish. This info needs to get integrated into the confluence document: https://confluence.lsstcorp.org/display/LDMDG/Triggering+a+Buildbot+Build
          Hide
          robyn Robyn Allsman [X] (Inactive) added a comment -

          This update contains a small change to the lsstswBuild.sh script in order to create a concordance table between the eups-tags and the buidlbot buildNumbers.

          The package may be found at:
          https://github.com/LSST/buildbot/commit/7e0a129d42bd8a28692741071723b59ac219004e

          You may educate me in the ways of github pull requests when I return from vacation.

          The change is documented for the users in: https://confluence.lsstcorp.org/display/LDMDG/Triggering+a+Buildbot+Build#TriggeringaBuildbotBuild-FindingConcordancebetweeneups-tagandbuildbot-number .

          Show
          robyn Robyn Allsman [X] (Inactive) added a comment - This update contains a small change to the lsstswBuild.sh script in order to create a concordance table between the eups-tags and the buidlbot buildNumbers. The package may be found at: https://github.com/LSST/buildbot/commit/7e0a129d42bd8a28692741071723b59ac219004e You may educate me in the ways of github pull requests when I return from vacation. The change is documented for the users in: https://confluence.lsstcorp.org/display/LDMDG/Triggering+a+Buildbot+Build#TriggeringaBuildbotBuild-FindingConcordancebetweeneups-tagandbuildbot-number .
          Hide
          frossie Frossie Economou added a comment -

          Hi, I assigned the review to Mario because the notion that I'd get enough time to figure out what an eups-tag is was a delusion. Happy to show you the github flow when you have returned to us - thank you Robyn.

          Show
          frossie Frossie Economou added a comment - Hi, I assigned the review to Mario because the notion that I'd get enough time to figure out what an eups-tag is was a delusion. Happy to show you the github flow when you have returned to us - thank you Robyn.
          Hide
          frossie Frossie Economou added a comment -

          Given this has been working in production, I declare unilaterally it has passed review.

          Show
          frossie Frossie Economou added a comment - Given this has been working in production, I declare unilaterally it has passed review.

            People

            • Assignee:
              robyn Robyn Allsman [X] (Inactive)
              Reporter:
              robyn Robyn Allsman [X] (Inactive)
              Reviewers:
              Frossie Economou
              Watchers:
              Frossie Economou
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Summary Panel

                  Time Tracking

                  Estimated:
                  Original Estimate - 1 day
                  1d
                  Remaining:
                  Remaining Estimate - 1 day
                  1d
                  Logged:
                  Time Spent - Not Specified
                  Not Specified