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

programatic way of determining latest bXXXX number

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Won't Fix
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: conda
    • Labels:
      None

      Description

      We need a programmatic means of determining the latest build id for that "master" branch that encompasses all top level products we want to product conda packages of. Ideally, this would be the latest "master" build that completed successfully but that may be non-trivial to determine with the current CI sestup.

        Attachments

          Issue Links

          blocks

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-4987 jenkins job to build conda packages

          • Won't Fix
          relates to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. DM-6213 Conda binary distribution improvements

          • Done

          Technical task - Created by JIRA Agile - do not edit or delete. Issue type for a technical task. DM-4819 investigate distributing automated lsst_apps builds via conda packages

          • Done

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            jmatt J Matt Peterson [X] (Inactive) added a comment -

            I'll talk to Josh about exact requirements but this seems like something I could implement in-between conda builds.

            Show
            jmatt J Matt Peterson [X] (Inactive) added a comment - I'll talk to Josh about exact requirements but this seems like something I could implement in-between conda builds.
            Hide
            Permalink
            mjuric Mario Juric added a comment -

            J Matt Peterson [X] – check out https://github.com/mjuric/conda-lsst/blob/master/bin/what-builds, if it can help. It will give you the list of bXXXX numbers that build a given product.

            It is a little bit more difficult to figure out if which branch the specific build came from. I think you'd probably do it by checking if the SHA1 of the product (which you'll find in the relevant manifests/bXXXX.txt file in versiondb) is contained in master (clone the git repo and do something like git branch --contains <SHA1>).

            Btw: the README.md of https://github.com/lsst/lsst_build describes the versiondb format (it should be in versiondb itself; mea culpa).

            Show
            mjuric Mario Juric added a comment - J Matt Peterson [X] – check out https://github.com/mjuric/conda-lsst/blob/master/bin/what-builds , if it can help. It will give you the list of bXXXX numbers that build a given product. It is a little bit more difficult to figure out if which branch the specific build came from. I think you'd probably do it by checking if the SHA1 of the product (which you'll find in the relevant manifests/bXXXX.txt file in versiondb) is contained in master (clone the git repo and do something like git branch --contains <SHA1> ). Btw: the README.md of https://github.com/lsst/lsst_build describes the versiondb format (it should be in versiondb itself; mea culpa).

              People

              Assignee:
              jmatt J Matt Peterson [X] (Inactive)
              Reporter:
              jhoblitt Joshua Hoblitt
              Watchers:
              J Matt Peterson [X] (Inactive), Joshua Hoblitt, Mario Juric
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.