v2 workflow migration
I am wrestling with the stability of Buildship.
Facing three major problems:
1. moving from v1 to v2 is still giving a lot of issues (see: https://www.loom.com/share/0d9ffa644d91490ba19d1e1024553aa1)
2. Having a lot of issues with scripts that were running correctly. And now they are not anymore. I'll show you one example in this video:
https://www.loom.com/share/64fe4ba9d6f24d1eaab01ab80ece2ab7
3. debugging script was in v1 very easy. Now I find it difficult. How do you work with this?
I would like to get a copy of my code to github to have a more secure backup of my data and the possibility to run my setup at a different server.
What are your experiences at the moment with Buildship?
6 Replies
Hi Albert,
Thanks for sharing these looms. Creating this thread to continue the conversation.
π Thanks! Just trying to get connected again to the product. Now I am moving away.
Sent you an email with permanent solutions to the above concerns, which will help build more trust and reliability in the product.
Also sharing some part of the email response here. for the community π
You can reply on the email for further conversation
We understand your concerns with stability and frustration here.
However, all of the issues you shared are related to workflows in V1.
1. Unexpectedly Failed workflows with error - cannot find module
2. Disappearing node values.
We request you migrate your V1 workflows to V2 to avoid the above major cornering issues. Regarding the highlighted error on the node field values you get after migrating your flow, it is because the triggers are not migrated, as we have updated all our triggers in V2 with advanced capabilities, you'll be required to add the trigger on the migrated flow and update the inputs and node field values accordingly.
We understand this does feel like a bit of work, but with v2 flows, we assure you of better stability and reliability with the product, with no chance of the BuildShip server going down.
Regarding your question about the backup of flows, this is already on our near future roadmap to allow you to export code and versioning with Git and manage with GitHub and GitLab, which will allow you to backup the code as well. For now, we provide version control for each workflow to restore a version of each flow. For now, we'll consider adding a feature for export workflow as a downloadable copy as a .json file. You can also copy-paste and store it on your local system as well - https://docs.buildship.com/copy-paste.
Sent you more details via email. Please reply to the email thread for more follow-up.
I would like to move from v1 to v2 or to be able to 'move' out from buildship.
I do not understand that my workflows break down when I migrate from v1 to v2. Migrating 'basic' triggers to 'upgraded triggers' isn't that difficult I asume?
There's so much work in all the details of the workflow, filling all the missing 'gaps' of the input variables is a lot of work. So moving from v1 to v2 without a proper migration tool, is not an option for me. Than I rather migrate away from Buildship. That's a lot of work as well. But after all the stability problems I faced with Buildship, that seems to be the better option.
Now I feel 'locked' in to a unstable version. And that's not a good feeling.
For me:
a. I simply want to get an export of all my workflows. So I have a free choice wether I migrate or not to v2 or outside buildship. Now I feel I am forced to put a lot of effort to migrate from v1 to v2, without having any other options.
b. or I want a proper tool to migrate from v1 to v2. Without script that brake down because triggers and input body values are not being migrated.
We'll take both of these items into consideration, and we're working on a video as well to show how to migrate efficiently and easily without breaking scripts.
We appreciate all the feedback received here.
Hi @mrAlbertZwolle Here's a video to check out - https://www.youtube.com/watch?v=MLy8oDlp3Go
BuildShip
YouTube
BuildShip Hot Tip #6 - Migrating BuildShip flow from V1 to V2
Migrate your BuildShip workflow to V2. Read about all the new features in V2 here: https://buildship.com/blog/buildship-v2
BuildShip is a low-code Visual Backend and AI Workflow Builder
Get started for free π https://buildship.com
Join the discussion π€
Chat: https://discord.com/invite/fjBugmvzZP
Tweets: https://twitter.com/buildshipapp
LinkedI...