Skip to main content
Archived

Continuous Integration

Related products:FME Flow
  • March 9, 2017
  • 4 replies
  • 53 views

Support for Continuous Integration.

Some of the things needed:

  • Possibilities to versioncontrol and merge fme-files (today this is a big problem due to that the "code" and the "gui" is mixed up and make it hard/impossible to merge)
  • Possibility to mock and write automated test
    • To run the test on a build server
    • What does a build server looks like for FME?
  • Separate configurations for different environments (eg. test, pre_prod and production)
  • Possibility to automate deployments
    • Including rollbaks
  • Best practice on how to write "the code"

4 replies

jpvo
Contributor
Forum|alt.badge.img+2
  • Contributor
  • March 17, 2017

Absolute necessity. I am currently doing it with VSTS. Solution build and automatic deployment is OK but we still can't automate unit testing.

Looking forward to have some improvement on that field.


  • October 11, 2018

I agree. The version control integration is somewhat covered in this suggestion (https://knowledge.safe.com/idea/18790/workbench-connects-directly-to-revision-control.html?smartspace=ideas-workbench). Although having the other suggestions here is a must for anyone in an agile software development environment. I have seen a product called rTest (https://github.com/Veremes/rTest) that has some potential for being a good testing solution for FME workspaces. It could be made more robust to work with a CI type system.


LizAtSafe
Safer
Forum|alt.badge.img+21
  • Safer
  • April 5, 2025
OpenArchived

LizAtSafe
Safer
Forum|alt.badge.img+21
  • Safer
  • April 5, 2025
This idea has been addressed in different released features. See https://support.safe.com/hc/en-us/articles/25407510327437-Getting-Started-With-CI-CD for more information. If you would like to see a different feature, please create a new idea