This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
FAQ
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Pipeline Versioning

stefany_king
New Contributor

‎03-30-2018 01:06 PM

Hello!

We have never used the Pipeline Versioning that is available in Snaplogic and are considering trying it. Currently if we need to make changes, we export our pipeline from our prod organization, import it into dev, update the naming convention with a new version (ex: v1_2), make our changes, export from dev and import to PROD and set everything back up to use the new pipeline. We tend to keep at least one version of the old pipeline in case we need to revert, so things are starting to get a little messy. We have some reservations about using the pipeline versioning tool, though, and would love to hear how it works for others. Our main concern is the visibility of changes using versioning instead of creating a whole new pipeline. Has anyone had any issues related to this? Are there any best practices we should follow when adopting pipeline versioning?

Thank you for the feedback!

0 Kudos
Reply
5 REPLIES 5

aleung
Contributor III

‎03-31-2018 09:54 PM

We use it and only have 1 pipeline within an env by using this versioning. You can always pull up any historical version of the pipeline if you like to compare to the changes with the current. There is a compare feature in case you are not aware.

We uses JIRA to track production changes and attached the pipeline so there is a system of record. You can even use Github to manage these source control if you wish.

0 Kudos
Reply

stefany_king
New Contributor
In response to aleung

‎04-02-2018 11:34 AM

Thank you for the feedback!

0 Kudos
Reply

lemo
New Contributor II

‎04-03-2018 08:57 PM

Just be aware that if you delete the pipeline then the versioning system will not help you. As of February 2018 4.12 release you can recover deleted assets from the recycle bin within 30 days, but after that time it’s gone forever. You can’t revert back to an earlier version of something that no longer exists!

0 Kudos
Reply

cstewart
Former Employee
In response to lemo

‎04-03-2018 09:52 PM

There is an interesting feature by which you can recover a deleted pipeline. If a pipeline has been deleted or changed, but there was an execution, when you click on the pipeline name in Dashboard (the Dashboard will show executions up to 60 days) then when you see the pipeline in Designer, it shows the pipeline which was actually executed, as it doesn’t exist any more, you can’t edit it, or save it. However you can export it!
Once exported, you can import it back in.
This gives you an extra 30 days after the pipeline is purged from the recycle bin.

Reply