โ04-27-2017 10:04 PM
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.
โ06-07-2017 11:49 AM
Thanks a lot C.J. Itโs really informative.