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.