cancel
Showing results for 
Search instead for 
Did you mean: 

Has Anyone Imiplemented a CI/CD Process Successfully?

mroldanvega
Executive Chef I
Executive Chef I

I would love to know if someone has implemented a fully automated CI/CD process that is working today. What tools are they using? How are they doing it? etc. Any suggestions?

2 ACCEPTED SOLUTIONS

maryhodges
Community Manager
Community Manager

Hey, there! We have an existing thread related to this topic here: https://systematic.workato.com/t5/workato-pros-discussion-board/hi-everyone/m-p/456/highlight/true#M...

Hope this helps!

Community Manager
Workato
https://www.linkedin.com/in/mary-yukari-hodges/

View solution in original post

jbashford
Deputy Chef II
Deputy Chef II

So using an external deployment tool (like Octopus Deploy or Jenkins) you could work across multiple workspaces and roll back versions of whole manifests automatically.  There are lots of things that need to be in place before you get there though (strict naming of assets, existing deployment infrastructure and established change control process).  Auto rollback would also require all of that to be hooked into a reliable monitoring system.

I did a Workato Happy Hour (not sure that's still a thing) on this subject a couple of years ago.  Would be happy to re-do that session for the Systematic Community if there is appetite.

View solution in original post

10 REPLIES 10

maryhodges
Community Manager
Community Manager

Hey, there! We have an existing thread related to this topic here: https://systematic.workato.com/t5/workato-pros-discussion-board/hi-everyone/m-p/456/highlight/true#M...

Hope this helps!

Community Manager
Workato
https://www.linkedin.com/in/mary-yukari-hodges/

Thank you, @maryhodges 

jbashford
Deputy Chef II
Deputy Chef II

I did back when I worked at Man Group.  This was before Workato had any recipe diff tools and all deployment had to be done in Recipe Lifecycle management.


I used Octopus Deploy Custom Powesrhell steps to call the Management API and pull down project manifests into a Git Repo and create a pull request.  Once an approver had signed off that request it was then deployed to the next Environment.  The final push to prod could then be done using one click in Octopus deploy.  Everyone involved was informed and given necessary links via Slack.

Although the solution worked well, it's not something I would recommend to my clients today.  It would be very difficult to replicate and offers very little over a semi manual process using the current tools.  Workato's lifecycle management is streets ahead of where it was 3 years ago. It's not perfect, but it's also not worth the effort of replacing given how fast it improves.

mroldanvega
Executive Chef I
Executive Chef I

@jbashford Thanks for your reply!
One of the things we have an issue with Workato's current features is that it has no API/automatic rollback capabilities. If a recipe is deployed and it is failing, someone needs to go and rollback to the previous version, but there's no mechanism to register this in Git, or open an issue. Also, Workato's capabilities don't allow to deploye cross Teams/Workspaces, only cross environments, so I'm kind of stuck there. 

Any recommendations?