Skip to main content
Question

Version Control of FME Files

  • December 20, 2025
  • 1 reply
  • 26 views

kokilam
Contributor
Forum|alt.badge.img+9

We require support to establish a structured version management and governance process for FME workspaces (.fmw files) using Azure DevOps (ADO).

Currently, FME files are updated manually, which creates challenges around version control, traceability, rollback, and collaborative development. We would like guidance and support on leveraging ADO repositories and pipelines to manage FME files effectively.

The objective is to:

  • Maintain version history of FME workspaces

  • Enable controlled check-in/check-out and collaboration

  • Support rollback and auditability

  • Align with enterprise DevOps and SDLC standards

Please advise on best practices, recommended repository structure, branching strategy, and CI/CD considerations (if applicable) for managing FME files in ADO.

1 reply

j.botterill
Influencer
Forum|alt.badge.img+56
  • Influencer
  • December 21, 2025

v\You can use FME Flow in a CI/CD pipeline and automate deployments, but version control integration is limited to GitHub (not Azure DevOps Git). I would recommend following the inbuilt version control that comes standard in FME Flow where you can commit, track, and restore workspace versions.

Best Practices: Safe Software recommends using FME Flow Projects for packaging workspaces and dependencies, which can be migrated between environments as part of a CI/CD process. You can use tools like Terraform or Azure Resource Manager templates for infrastructure automation.

For Azure DevOps, you’ll need to use custom scripts or REST API calls to automate workspace deployment and management.

https://support.safe.com/hc/en-us/articles/25407388445965-Leverage-Projects-within-CI-CD-process-flow

Using Pipelines: