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

Leverage Git servers that enable allowReachableSha1InWant for custom builds instead of always doing a full fetch

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Repository (Git)
    • None
    • 2
    • 4

    • 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.

      Problem Definition

      Running a custom build in Bamboo with a specific revision will always perform a full fetch. Since Git 2.5, Git servers can enable uploadpack.allowReachableSha1InWant to allow fetching from a reachable SHA1.

      Bitbucket Server supports it since 5.5.

      Suggested Solution

      We could cut down checkout times for custom builds if we tried to fetch from the specific SHA1 and only falling back to a full fetch if it fails.

            [BAM-20737] Leverage Git servers that enable allowReachableSha1InWant for custom builds instead of always doing a full fetch

            SET Analytics Bot made changes -
            Support reference count Original: 3 New: 4
            SET Analytics Bot made changes -
            Support reference count New: 3
            SET Analytics Bot made changes -
            UIS Original: 1 New: 2
            SET Analytics Bot made changes -
            UIS Original: 2 New: 1
            SET Analytics Bot made changes -
            UIS Original: 15 New: 2
            SET Analytics Bot made changes -
            UIS Original: 2 New: 15
            SET Analytics Bot made changes -
            UIS Original: 1 New: 2
            SET Analytics Bot made changes -
            UIS New: 1
            Jeremy Owen made changes -
            Link New: This issue is related to BAM-14706 [ BAM-14706 ]
            Jeremy Owen made changes -
            Description Original: h2. Problem Definition
            Running a custom build in Bamboo with a specific revision will always perform a full fetch. Since Git 2.5, Git servers can enable {{uploadpack.allowReachableSha1InWant}} to allow fetching from a reachable SHA1.

            Bitbucket Server supports it since 5.5.

            h2. Suggested Solution
            We could cut down checkout times and load on repository servers for custom builds if we tried to fetch from the specific SHA1 and only falling back to a full fetch if it fails.             		New: h2. Problem Definition
            Running a custom build in Bamboo with a specific revision will always perform a full fetch. Since Git 2.5, Git servers can enable {{uploadpack.allowReachableSha1InWant}} to allow fetching from a reachable SHA1.

            Bitbucket Server supports it since 5.5.

            h2. Suggested Solution
            We could cut down checkout times for custom builds if we tried to fetch from the specific SHA1 and only falling back to a full fetch if it fails.

              Unassigned Unassigned
              jowen@atlassian.com Jeremy Owen
              Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: