Skip to Main Content
Cloud Platform


This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Future consideration
Workspace UrbanCode
Categories Deploy
Created by Guest
Created on Nov 19, 2021

Update "Git Source Control" Plugin to use Sparse Clone for Component version creation

Currently the plugin will clone an entire repository regardless if the include/exclude parameters when creating a new component version.

This means that the the entire repository is cloned to the agent directory before then making use of the includes/exclude parameters to determine what to include in the version.

In our case this means that we require to clone 340,000 files locally (~500Mb) when the include parameters may limit the elements to be included to 100-200.

Idea priority High
  • Admin
    Osman Burucu
    Dec 2, 2022

    Thank You for your feedback. I will check with Development

  • Guest
    Nov 29, 2022

    git sparse checkout has been experimental for at least 12 years, and there are other vendor products that happily exploit the capability. It's use would massively improve the performance on UCD when large repos are involved.

    Can you please review this decision.

  • Admin
    Osman Burucu
    Nov 24, 2022

    git-sparse-checkout:

    THIS COMMAND IS EXPERIMENTAL. ITS BEHAVIOR, AND THE BEHAVIOR OF OTHER COMMANDS IN THE PRESENCE OF SPARSE-CHECKOUTS, WILL LIKELY CHANGE IN THE FUTURE.


    As we cannot support experimental features of git this feature will be considered for future releases as soon as git officially supports sparse checkouts