Skip to main content
Solved

Code Repository For Managing Scripts Across Servers

L
Forum|alt.badge.img
  • lc

In a situation where multiple FME servers are spun up and run standardized workbenches, what's the recommendation for managing helper scripts? We have a set of Python scripts that aid the startup/shutdown of these workbenches. But having multiple servers, it is difficult to ensure the versions of these scripts are the same across the board. Anyone have any recommendations for a code repository?

We do have a subscription to Visual Studio Team Service. If anyone has used VSTS with FME server, I am interested to hear about your experenice in that as well.

Best answer by fmelizard

If the use case is moving solutions from Development to Staging to Production environments, then this Q&A; might be of use:

 

https://knowledge.safe.com/questions/35716/how-can-i-move-a-solution-from-my-development-envi.html?childToView=50984#answer-50984

 

 

In short, I'd consider placing the python scripts in a Resources directory on FME Server and then moving them and other parts of your solution with the Projects feature in FME Server (2017.0 or newer). I'd be interested in feedback on that idea.

View original
    Did this help you find an answer to your question?

    5 replies

    L
    Forum|alt.badge.img
    • larry
    • August 16, 2017

    Maybe you can modify the FME Server Engine resource to point to a common share used by all your FME Server and make sure this share is always updated with the latest version of the code.

    What we have internally here is a custom tool monitoring source control check-ins (Subversion) and taking care of redeploying the code (workspaces, custom transformers, python file and any configuration change (role, users, notification, schedule)) as soon as there is a change.

    L
    Forum|alt.badge.img
    • lc
    • Author
    • August 16, 2017

    Thanks @larry. Unfortunately I don't have the permissions to make that happen. I could potentially set up a workbench that crawls the various servers to monitor/push new versions of the code...!

    david_r
    Celebrity
    • david_rCelebrity
    • August 17, 2017

    If you keep your common scripts in a version management system such as Git or SVN, it would be fairly easy to set a scheduled task on each server to update them daily (e.g. a nightly 'git pull').

    M
    Forum|alt.badge.img+2
    • mark_f
    • August 17, 2017

    deleted answer

    fmelizard
    Safer
    Forum|alt.badge.img+18
    • fmelizardSafer
    • Safer
    • Best Answer
    • August 18, 2017

    If the use case is moving solutions from Development to Staging to Production environments, then this Q&A; might be of use:

     

    https://knowledge.safe.com/questions/35716/how-can-i-move-a-solution-from-my-development-envi.html?childToView=50984#answer-50984

     

     

    In short, I'd consider placing the python scripts in a Resources directory on FME Server and then moving them and other parts of your solution with the Projects feature in FME Server (2017.0 or newer). I'd be interested in feedback on that idea.

    Reply


    Helpful Members This Week

    Community Stats

    31,300
    Posts
    118,696
    Replies
    38,880
    Members

    Latest FME

    Terms & ConditionsCookie settings

    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
    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.