Skip to main content
Archived

Automatically create a commit when publishing/republishing a workbench to Server

Related products:FME Flow
  • June 27, 2018
  • 4 replies
  • 86 views
cfvonner
Supporter
Forum|alt.badge.img+27

***Note from Migration:***

Original Title was: Automatically create a commit when publishing/republishing a workbench to Server


The current version control implementation in FME Server is pretty good. I'd like to see it integrated into the FME Desktop publishing workflow too. If you have enabled version control on the FME Server, it would be nice if each publish/republish from FME Desktop automatically resulted in a commit. That would require allowing the user to enter a commit message somewhere in the publish/republish dialog boxes.

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.

4 replies

sigtill
Supporter
Forum|alt.badge.img+25
  • sigtillSupporter
  • Supporter
  • June 28, 2018

This would be great - so whenever 1-4 persons works on and uploads the same workspace to server it can check if you have the latest workspace downloaded - and upload only if it is newer. In that way if someone else have uploaded a version before you downloaded it, then you have to download their version and "merge changes" manually before uploading again.

The real SigTill
runneals
Enthusiast
Forum|alt.badge.img+29
  • runnealsEnthusiast
  • Enthusiast
  • May 22, 2019

Correct me if I'm wrong @sigtill, but versioning (how it's implemented in its current state on FME server) doesn't have the capability to compare versions.

runneals
Enthusiast
Forum|alt.badge.img+29
  • runnealsEnthusiast
  • Enthusiast
  • May 22, 2019

Second this! As an advanced user, I know how to commit edits, but those with a more basic working knowledge may not. It would be nice if it would also include the history parameter as the commit message by default as well (or have a method of pushing the commit message into the history parameter).

cfvonner
Supporter
Forum|alt.badge.img+27
  • cfvonnerSupporter
  • Author
  • Supporter
  • May 22, 2019

Not directly. But if you have access to the FME server disk where the repository sits, and you install a Git client, you can use the Git tools to do a compare. However, you would just be able to see the changes in text format, not a graphical workbench canvas.

Community Stats

32,749
Posts
124,193
Replies
41,251
Members
Terms & ConditionsAccessibility 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.