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.


