We have enabled Version Control to an external repository on FME Flow. Are there any best practices for managing Workbenches in development in FME Form?
My current thought, which I haven't spent much time developing, is to recommend that once a Workbench is uploaded to Flow, the desktop version is archived and any future work on the Workbench must be done by Downloading from Flow and Republishing. Basically, to insist that all work must be done from Workbenches from Flow.
The downside I can see from this is that there is no way to force developers to follow that. Any suggestions?
Best answer by hkingsbury
That approach can work, it then tranisitions into a training and management exercise - ensuring proper process is followed.
Safe is improving the version capabilities of the software as we speak, and beginning to integrate more and more GIT and version control into it
There were a couple of really good slides and presentations on version control in Bonn earlier this year, I can't find the exact one I'm looking for, but this presentation from Tensing was really interesting
There were a couple of really good slides and presentations on version control in Bonn earlier this year, I can't find the exact one I'm looking for, but this presentation from Tensing was really interesting
There were a couple of really good slides and presentations on version control in Bonn earlier this year, I can't find the exact one I'm looking for, but this presentation from Tensing was really interesting
I wasn't able to attend this year at Bonn. Hopefully, I'll be able to attend 2024.
I'm excited to see the work that Safe is doing on integrating version control between Flow and Form. An end-to-end version control from Workbench inception in Form to final Flow repository will be a great improvement for CI/CD workflows.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
