Allow GIT or Subversion to be used as a revision controlled repository for workspaces, and Workbench interacts directly with that system when saving workspaces.
This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
I'm less concerned about transformer positioning, but yes, I think metadata-like items are important. I think anything that's text-based should be compared, and if there have been changes, you should be prompted to merge. If a comment is the same, but someone has appended to the comment, then that should merge without review. That's how a source control would work. It's only where there are conflicts e.g. both people have modified the comment that it matters.
+7For a useful collaborative revision control (that allows for easy merging of other users changes to a workspace), I believe that it would be a good idea to make the FMW format true XML. A positive side-effect would be that it becomes more readable and allows people to build custom tools to automate/edit their workflows.
But that's probably going to be too much of an overhaul?
+8- Contributor
Functional and metadata change comparisons when merging are the most critical. Cosmetic changes less so, though it would be nice to be able to track those too at some point...lower priority.
Be aware that different companies standardize on different version control systems, so having to pick one might be too restrictive. However, if you do have to pick one, git is probably the best choice. It’s what I use for most projects. Though I have temporarily switched to subversion for FME projects because it can lock workspace and transformer files, preventing merge headaches for teams. Once FME supports full merge capabilities, I’ll switch back to git.
+10Hi @TiaAtSafe
I was thinking about a simpele option that would allow to store the history with the workspace. I might not be a fancy github integration, but just a simpele option. Perhaps with the possibility to empty the history and to have date/time visible with each change.
+17- Contributor
Hi @lars_de_vries, thank you for your comment! Are you thinking something like the history window that exists in Workbench already but a little more robust? Including the date/time as well as exporting it would provide a workspace change log almost.
+10Hi @TiaAtSafe
Yes, that was exactly what I had in mind.
Per session a history is kept, so why not save it with the Workspace. Maybe an option per workspace to keep the history or not. If 'Keep history' is checked, I can imagine a dialog comes up to give a version nr for that session and optionally set an author name, or the user-login.
This would be a great idea. We are activity pushing all our workspaces into Git (via Team Foundation Server). We are also trying to establish some sort of code review process through Pull Requests. Having the ability to interface with Git via the Workbench would be much easier than using another tool such at CLI to push/pull code. Would also be nice if there was a way to easily compare commits, branches, etc. within Workbench. Currently, we can only compare the resulting XML workspace files. You loose some context in doing this compared to viewing a workspace within Workbench.
- Contributor
Any progress or news around this topic? It would be really helpful for support of FME workspace development to be able to easily track changes between workspace versions and make comments or do review. Right now it is very hard to see what has changed.
What if you would have a visual revision interface inside FME Workbench where you could choose a previous version from a repository (FME Server, Git, TFS, etc.) and directly see all changes between these documents (added transformers, changed parameters, etc.), like a pull request. Maybe then you could be able to click on these state difference points and got some highlighting on the canvas to show the differences. And choose a state difference point and make a comment for the developer. And at some point you could choose to accept the differences and commit to the main branch.
Just some ideas. I know it probably would not be easy to build this, but at Safe you are always in for a challenge right? :-)
+17- Contributor
Can't make any commitment yet, but we've got some good ideas near the very top of a board here related to this...
+3- Safer
@g_karssenberg, @rsmith, @lars_de_vries, @jeffshobbs, @sander, @kweller, @patrick_koning, @sigtill, @jdh, @marko, @nic_ran, @julien, @samuelvaldez, @david_r, @cfvonner
We are kicking off a project to improve our understanding of our users' needs and challenges, when it comes to managing different workspace versions. We would love to chat with you. Your input will have a direct impact on FME's future.
If you have 20-30 minutes to chat between April 13th - 15th, please pick a time on this form.
In addition to helping us shape FME's future, you'll also be taking part in a fun Safe tradition: "Innovation Daze". As some of you may know, every year around this time, Safers spend a week working on projects they normally don't have time to work on. Many of FME's great innovations are results of the work we do during "Innovation Daze". See this blog, if you want to learn more about this tradition. It's Innovation Daze at Safe this coming week. And, one of our projects' goal is to better understand our users' needs and challenges around workspace version management. So, by talking to us, next week, you'll be joining us in this fun Safe tradition!
+24- Contributor
A suggestion for a git or TODO-list within FME Desktop itself is suggested here, and might be easier to implement and add additional benefits? : https://community.safe.com/s/bridea/a0r4Q00000JC7rTQAT/a-possible-way-to-improve-working-with-fme-workspaces-and-informing-the-enduser
+20- Contributor
What is the current status of this? Would love to see this implemented into FME 😍 !
+14- Supporter
I am also curious what is the current status of git integration with fme workbench.
I have got colleagues who are really looking forward to this functionality
Helpful Members This Week
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.