Date: Tue, 19 Mar 2024 05:43:52 +0000 (UTC)
Message-ID: <44342161.37.1710827032318@575423a5252a>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_36_484773266.1710827032318"
------=_Part_36_484773266.1710827032318
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Copying or Migrating a Pipeline
Copying or Migrating a Pipeline
Copy a Pipeline&nbs=
p;to another Project or Org to modify it without impacting the original Pip=
eline. Follow these best practices for any child Pipelines and Assets =
that the copied Pipeline references:
- If the Pipeline has one or more=
child Pipelines, copy them to the same Project.
- If the Pipeline contains refere=
nces to other Pipelines, Files, Accounts, or Tasks (which can be called fro=
m a Snap), handle them as follows:
- Leave references to Assets in t=
he global shared folder.
- For Assets in a Project other t=
han the destination Project:
- If the reference to a File is a=
n absolute path, do not change it.
- If the Asset is available in th=
e destination Project, change the reference to point to the destination pro=
ject after copying the Pipeline.
- If the destination Project does=
not have an Asset with the same label, but one exists in its =
shared folder or the global shared folder, change=
the reference to the appropriate location after copying the Pipeline.
- If the Asset has a different la=
bel in the destination Project, change the reference before moving the Pipe=
line.
The Designer and Manager toolbar=
s both include copy buttons, but the functionality differs:
- From Designer, you can copy the=
open Pipeline to a different Project in the same Org.
- From the Manager Asset table, you can select one or more Pipelin=
es and copy them to a different Project in the same Org or to a different Org.
------=_Part_36_484773266.1710827032318--