Can we get "Run a Pre-Deployment Script" please?

[HighPower_Matt]

Hey dudes,

For each Deployment, we have a “Run a Post-Deployment Script” option, which we use to mark a server as online again and available for users, among other things.

It’s great.

But we don’t have an elegant way to automatically mark a server as offline at the start of the process. I think this could be solved by giving us this ‘pre-deployment script’ ability.

I did already read this request:

Run a Pre-Deployment Script on Source Server

I am dearly missing this feature because the first step in our pipeline is an internal deployment (from DEV to a preparation stage). To maintain a consistent build number and timestamp, these should be added on DEV. Alternatively, the deployment could refer to an actual build (by ID) where a pre script can already be set. While I am at it, I can also think of a few useful applications for a pre script running on the destination server. If there was a way to incorporate actual script results, th…

… and it’s really not the same, as what I’m asking truly is just on the Deployment (not on a Build / source server).

[john_r]

Admin API to expel all users and then set Block New Users?

[HighPower_Matt]

We use a central login DB file with a nicer UI than what FMS could provide with that.

[HighPower_Matt]

Looks like v4.7.0 added this feature. Thanks!!!

OttoFMS now has support for a pre-deployment script. This is very similar in setup to post-deployment scripts, just with a different results filename and it will default to prevent your deployment if the pre-deployment script fails or does not return a “done” results file. This script is run before files are closed during the deployment.