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.
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!
This would be extremely helpful! We use Azure DevOps for doing agile and setting up pipelines for deployments. I haven't been able to do this with FME because the only option for Version Control is GitHub...and there's no easy way to integrate a Repo in Azure DevOps with the Repositories in FME Server. We'd like to streamline this.
Hi, we use Azure Devops which has the ability to generate GIT URLs and Personal Access tokens, but doesn't appear to be compatible with FME Server. We would love this to be implemented.
Our company has just mandated that no-one is to use github for work related code storage, due to it being scraped for use in github co-pilot. https://github.com/features/copilot
This means we now have no external automated repo for workbench backups, and are going to have to create a scheduled task in fme server to push our workbenches somewhere else using rest api's.