mrAlbertZwolle Comments

mrAlbertZwolle

•Created by mrAlbertZwolle on 2/13/2025 in #💬・general

v2 workflow migration

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.

6 replies

BBuildShip

•Created by mrAlbertZwolle on 2/13/2025 in #💬・general

v2 workflow migration

🙂 Thanks! Just trying to get connected again to the product. Now I am moving away.

6 replies

BBuildShip

•Created by mrAlbertZwolle on 3/16/2024 in #❓・buildship-help

Loop question

I fixed it myself. Changed the JSON to: [ { "ChapterTitle": "Chapter 1", "Type": "[Type]", "Description": "Description" }, { "ChapterTitle": "Chapter 2", "Type": "[Type]", "Description": "Description" } ]

5 replies

BBuildShip

•Created by mrAlbertZwolle on 3/16/2024 in #❓・buildship-help

Loop question

any one?

5 replies

BBuildShip

•Created by mrAlbertZwolle on 3/14/2024 in #❓・buildship-help

Is it a bug or do I do something wrong? Try to add parameters to a value field.

thanks so much!

10 replies

BBuildShip