Skip to Main Content
IBM Cloud - Structured Ideas


This portal is to open public enhancement requests against IBM Cloud and its 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.

IBM Cloud Support Center (https://cloud.ibm.com/unifiedsupport/cases/form) – Use this site for any IBM Cloud defect or support need.

Stack Overflow (https://stackoverflow.com/questions/tagged/ibm-cloud) – Use this site for IBM Cloud technical Q&A using the tag "ibm-cloud".

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

Status Under review
Created by Guest
Created on Oct 2, 2024

Migrate and/or Clone a Single Classic Delivery Pipeline from one ToolChain to another ToolChain

When we are using the Delivery Pipeline in IBM ToolChain, we usually separate the Pipelines into different ToolChains, such as Development, Approval/Testing and Production.


Every time a new Pipeline is needed, we need to manually create the new Pipeline and its respective stages and each of its configurations, including variables.


It is necessary to include the functionality of cloning an existing Pipeline within the same ToolChain (not just the stage, which is always different), as well as cloning/migrating a Pipeline from one ToolChain to another, in addition to allowing the use of global variables for all Pipelines in the ToolChain, such as the environment variables in the DEVOPS_GIT / DEVOPS_GIT_TOKEN Pipeline configuration, which is usually common to all Pipelines in the environment.

The GITLAB token, for example, is valid for 1 year. When it expires, it is necessary to exchange it in all Pipelines because we do not have a global variable for the ToolChain.


This type of activity will speed up the creation of new Pipelines that pass through more than one ToolChain, reducing the time of activities from 1 hour to 5 minutes, for example.

Idea priority Urgent
Needed By Yesterday (Let's go already!)