Skip to main content
Open

Enable compulsory commits when publishing/republishing a workspace to Flow

Related products:FME Flow
  • August 6, 2024
  • 1 reply
  • 23 views
dave_seamless
yldbooysen
danilo_fme
warrendev
birgit
+1
  • dave_seamless
    dave_seamless
  • yldbooysen
    yldbooysen
  • danilo_fme
    danilo_fme
  • warrendev
    warrendev
  • birgit
    birgit
  • revesz
    revesz

yldbooysen
Contributor

Version control is only as good as the business processes surrounding it - being able to commit to a git repo/FME version control is great, but it’s easy to miss in a publishing workflow and is not currently possible to enforce.

In order to support more robust SDLC & change control processes, it would be extremely useful to be able to either automate a git commit when publishing/republishing a workspace, or to configure a workspace/repo/flow env to make commits compulsory.

My blue-sly vision for this would be that the configuration is set at the repository level on FME Flow, and in repos where compulsory commit is enabled, the publish action in FME Form cannot be used until a commit has been performed with the current version of the workspace.

1 reply

LizAtSafe
Safer
Forum|alt.badge.img+15
  • Safer
  • September 5, 2024
NewOpen

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings