Duplicate of Workbench connects directly to revision control
Released
Workbench Versioning. aka GIT experience. Important for serious developments
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, 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 an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, 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.
+4- Safer
2 groups mentioned this. Was unanimous that this is a big deal whenever you are working on big project with source code control
I'm just wondering if FME Server has similar function to TFS. I have been using TFS for workbench repository as it's safe for source control by checkingOut, locking and checkingIn with no risk at all. However, we have an FME Server up and running and wonder if I can do the same activity as with TFS for workbench edits.
Any ideas please.
+5A few ideas about this posted, I'm massively in favour any sort of versioning system and it would be much better then the present upload service. It can be difficult to keep track of the development of large workspaces. Auto back up of old uploads with time stamps would be a great feature and if you could see old edits with the abiulity to add notes within FEM Server rather then in the workspace almost like a metadata editor.
Perhaps the best way of using FME Server as a central safe source code repository would be that once the .fmw downloaded from the server and edited, it has to be saved as a version and publish the edited version back to the same Workspace repository in the server. So, it will be like ISV3_v1.fmw & ISV3_v2.fmw ,,,,,,etc.
I'd like to be able to set up FME so that it integrates with our GIT. Thinking that when a job is run on server it could be set up to pull from git to ensure the fmw is the latest greatest. Development using workbench would allow you to pull from a git similar to the way that it can currently pull from FME Server. Ditto for commits / saves. They would get saved to GIT. FME server would automatically pick this up.
Would also be really nice for python code / modules to be integrated with GIT. Currently we develop our python code, commit to our GIT. Then have a production directory that our workbench will use for our customizations. That directory is easy to keep up to date with a simple pull from the repository. FME server however is much trickier to update. My approach so far has been to write a script that mirrors the contents of our production directory to fme server. Would be better if fme server could be set up to pull from git and stick the python code where it needs to go for fme server to be able to consume it.
+13- Safer
While this hasn’t been added directly into Workbench, we have added support for Version Control to FME Server for 2017.1. With this, it would be possible to upload your workspaces to FME Server and use it to keep track of your workspace versions.
This idea: https://knowledge.safe.com/idea/51410/version-control-in-fme-server-next-steps.html contains a video of how to work with FME Server Version Control and what to do if you don’t already have FME Server. If you’re interested, please try it out and give us your feedback through the idea.
+1- Participant
I still *really* would like to have FME Workbench integration with Git (and GitHub). Is Safe working on this for a future release?
+11- Safer
@guy_lafleur, @friesewoudloper, @davidpark, @marko
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!
Login to the community
No account yet? Create an account
An FME Account is required to contribute
LoginEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.