cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

Introducing new versions of common pipelines

cj_ruggles
New Contributor III

Hi,

We have a common Error Handler pipeline which we are developing for use across all projects. When I create a new version of the Error Handler, I donโ€™t want to just update it directly in our DEV environment as other developers will be inconvenienced if it breaks their pipelines.

I can create a separate copy (e.g. โ€œError Handler Newโ€) and then ask each project to migrate across to it - however then we end up with all projects pointing at โ€œError Handler Newโ€ and there is no easy way to rename this back to โ€œError Handlerโ€ without asking every project to repoint their pipelines again.

We could just incrementally name the common pipelines (e.g. โ€œError Handler v1โ€, โ€œโ€ฆv2โ€, โ€œโ€ฆv3โ€, etc.) however weโ€™d prefer not to as weโ€™d rather manage versions in our source code repository, not in Snaplogic.

Any suggestions of how to better manage the introduction of new versions of common pipelines?

Thanks,
C.J.

5 REPLIES 5

vyasyash
New Contributor III

Thanks a lot C.J. Itโ€™s really informative.