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

lsst_build git fetch/clone retrying

    Details

    • Templates:
    • Story Points:
      3
    • Epic Link:
    • Team:
      SQuaRE

      Description

      We occasionally observe a "wave" of github fetch/clone failures from lsstsw / lsst_build in the jenkins env. Where a wave is several random failures over the course of a day or two and then there are no failures for weeks. I am convinced that these are on the github end as I have experienced clone failures when running lsstsw outside the the jenkins env.

      I am loath to retry the entire jenkins build upon any failure as this might result in a legitimate build failure unnecessarily tying up build slaves. There are two solutions that occur to me:

      1) propagate errors up from lsst_build in such a way that the CI driver can determine the reason of failure and retry a set of failure modes

      2) add git fetch/clone retrying support into lsst_build

      I am leaning towards #2 as the implementation is straight forward and contained within a single component.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jhoblitt Joshua Hoblitt
                Reporter:
                jhoblitt Joshua Hoblitt
                Watchers:
                Angelo Fausti, Jim Bosch, Jonathan Sick, Joshua Hoblitt, Robert Lupton, Russell Owen, Simon Krughoff
              • Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Summary Panel