Managing Versions and Deploying Pipelines

[jcross]

Is there a best practice document or can someone provide an example of how you’re managing pipelines from development, through a test/QA phase and into Production?

We have two orgs crated, one for dev/qa and one solely for production. I’m interested to know how people are managing their pipeline development projects and migrating them to an environment in which to do QA testing before deployment to production.

How are you managing the pipelines, files, etc. between Dev and QA?

I’m also interested in if anyone is using GitLab to store ‘code’ outside of SnapLogic.

[abew]

jcross:

there a best practice document or can someone provide an example of how you’re managing pipelines from development, through a test/QA phase and into Production?

We have two orgs crated, one for dev/qa and one solely for production. I’m interested to know how people are managing their pipeline development projects and migrating them to an environment in which to do QA testing before deployment to production.

How are you managing the pipelines, files, etc. between Dev and QA?

I’m also interested in if anyone is using GitLab to store ‘code’ outside of

Thanks! As far as automating moving pipelines across environments, is the only thing we can do is using the Management API?

[stevegoodwin]

You can write pipelines using the snaplogic metadata snap pack to list, read, create, update assets.

This allows a user to create their own CI/CD workflow