Skip to main content
  • EN

Hi everyone,

on my local machine, I have installed multiple FME versions (2023.2.6, 2024.2.4 & 2025.0). In our company we work extensively with git and i use the Workbench Git integration from the command line. 

However, if I want to diff Workspaces that were modified with the newer versions (only tested for 2025.0) the command “git diff” launches FME 2023.2.6. This is not useful, because if there are e.g. Transformers that have a newer version, i guess one that is not supported in the older versions, the “Compare Workspace” Tool (2023.2.6 version) cannot display them.

Is there a way to specify which version of FME should be used when executing the git diff command?

 

Thanks for your help

Cheers!

Hello ​@stadimarmiladi ,

As mentioned in step 2 of the tutorial

https://support.safe.com/hc/en-us/articles/25407730429453-Workbench-Git-Integration-from-the-Command-Line

your (desired) FME installment should be registered in the PATH environment variable. There is no way to dynamically choose the version. The one set in PATH is the one used by the git_merge and git_diff scripts.

Never say never of course as you might craft different scripts .gitconfig and .gitattributes to link different versions of FME to differend repositories (with workspaces of corresponding origin).

Hope this helps..

Kind regards,

Martin

I’m having the same issue. We are working on several projects for different clients all using different FME versions. In the end we may have anywhere between 5-10 FME versions on our laptops and we can’t reasonably manipulate the PATH every time.

I’ve made a PoC that replaces the provided shell scripts with a Python script. This is what it does:

  • Parses both the old and new version of the .fmw and looks for the build number in the LAST_SAVE_BUILD setting
  • Keeps the max build number from the old and new versions
  • Looks in the Windows registry to find the FME installation that has a build number that is closest but greater-than-or-equal to the bild number from the previous point
  • uses the fmeworkbench.exe from this FME_HOME to compare the workspaces

It does work, but it feels clunky. Also, the PoC only works on Windows.

 

Community Stats

31,926
Posts
121,264
Replies
39,553
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.