• Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • 3.4
    • None
    • None
    • 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.

      TDB

            [BAM-10048] Submodules caching

            mark-1003 added a comment -

            New ticket is BAM-17878
            Please vote if You are interested in this feature!

            mark-1003 added a comment - New ticket is BAM-17878 Please vote if You are interested in this feature!

            You can obtain the submodule url, check it out to a cached location, then modify the url in the build dir clone. Is that not feasible? One thing is for sure: you do have control. I don't understand why you need control over where submodules originate. As long as you have access to it, you can mirror it locally. Then from that point on, just pull Deltas

            Robert Dailey added a comment - You can obtain the submodule url, check it out to a cached location, then modify the url in the build dir clone. Is that not feasible? One thing is for sure: you do have control. I don't understand why you need control over where submodules originate. As long as you have access to it, you can mirror it locally. Then from that point on, just pull Deltas

            It's not just about the complexity of implementation. Submodules are handled by git itself and we don't have control over the source from which they are retrieved.

            Przemek Bruski added a comment - It's not just about the complexity of implementation. Submodules are handled by git itself and we don't have control over the source from which they are retrieved.

            Very disappointing that this won't be addressed. We're moving stash to the cloud but keeping bamboo in house. This will result in crazy bandwidth issues and slow builds because submodules are cloned remotely each build. Submodules are pretty common and to not do it because it is "complex" feels like an excuse.

            Robert Dailey added a comment - Very disappointing that this won't be addressed. We're moving stash to the cloud but keeping bamboo in house. This will result in crazy bandwidth issues and slow builds because submodules are cloned remotely each build. Submodules are pretty common and to not do it because it is "complex" feels like an excuse.

            Hi jgiles@atlassian.com,

            It's very unlikely that we will change our decision on this due to the complexity of the work required. We have competing priorities today and it will be really hard for us to schedule this improvement.

            Thanks,

            Sten
            Product Manager

            Sten Pittet (Inactive) added a comment - Hi jgiles@atlassian.com , It's very unlikely that we will change our decision on this due to the complexity of the work required. We have competing priorities today and it will be really hard for us to schedule this improvement. Thanks, Sten Product Manager

            James Giles IV (Inactive) added a comment - spittet xtjhin - Is this something we'd be willing to revisit? https://support.atlassian.com/browse/BSP-23932?focusedCommentId=7772464&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-7772464

            No separate caching for submodules.
            Should be defined as additional repository, when such level of details is required

            Marek Went (Inactive) added a comment - No separate caching for submodules. Should be defined as additional repository, when such level of details is required

              Unassigned Unassigned
              mwent Marek Went (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: