Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-7437

Git repo should use shallow clones instead of full clones.

    XMLWordPrintable

Details

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      Currently we use full clones during:

      • collecting changes, on bamboo server
      • code retrieval, on agents, during performing build

      In both cases we don't need the whole history, so if it is possible we should do shallow clones.

      Shallow clones are not implemented in JGit yet.

      Also - both server and agents should be able to fetch afterwards properly. Corner test case:

      • detecting new rev A -> add to queue
      • detecting new rev B (grandchild of A) -> add to queue (concurrent builds are on)
      • agent -> takes rev B, does shallow clone on it (so it won't have rev A)
      • agent -> takes rev A, does fetch - in such case agent should somehow obtain rev A

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              pstefaniak PiotrA
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: