Recurring Deployments
Run a deployment automatically on a repeating schedule, such as every night or every Friday, by scheduling it in OttoDeploy and setting the frequency in the FMS Admin Console.
Recurring deployments let you run the same deployment on a repeating schedule, such as refreshing your development server with production data every Friday night. Recurring deployments require OttoFMS 4.4.0 or later.
There is no "repeat" option in OttoDeploy. You make a deployment recurring in two parts: schedule it once in OttoDeploy, then change that schedule's frequency in the FileMaker Server Admin Console. OttoFMS handles the rest.
Creating a Recurring Deployment
Set up your deployment in OttoDeploy
Set up your deployment in OttoDeploy as normal. Deployments with multiple sub-deployments and all deployment options are supported.
Schedule the first run
On the Review & Deploy screen, choose Schedule for Later and pick the date and time you want the first run to happen. Scheduled times use the destination server's timezone. See Sending Deployments for more on this screen.
At this point you have a one-time scheduled deployment. OttoFMS creates a FileMaker Server script schedule on the destination server that is set to run once.
Find the schedule in the FMS Admin Console
On the destination server, open the FileMaker Server Admin Console and go to Configuration > Script Schedules. The schedule OttoFMS created is named Otto_<deployment_name>_<5 random characters>.
Change the schedule's frequency
Edit the schedule and change its frequency from running once to the repeat pattern you want, such as daily or weekly. You can also change the start time and the schedule name. Save the schedule.
Do not change the script or the script parameters on the schedule. OttoFMS uses them to find the deployment to run, and the schedule will fail if they are changed.
Your deployment will now run on the schedule you set. You can confirm it is set up by checking the Deployments page in the OttoFMS console on the destination server, which shows the upcoming scheduled deployment.
How Recurring Deployments Work
At any time, a recurring deployment shows up as a single upcoming scheduled deployment in the OttoFMS console. When the FileMaker schedule fires:
- OttoFMS runs the scheduled deployment.
- OttoFMS creates a new scheduled deployment with the same settings for the next run.
- OttoFMS updates the FileMaker schedule to point at the new scheduled deployment.
Because of this, the scheduled deployment you see in the OttoFMS console is replaced after every run. The previous run appears in your deployment history like any other deployment.
Each run pulls a fresh source
Every run pulls from the deployment's source again. It does not reuse the files from the first run. For example:
- A deployment using a just-in-time build creates a new build and pulls fresh copies of the source files on every run.
- A deployment using Build from Inbox uses whatever build is in the destination server's inbox when that run starts.
This is what makes patterns like a weekly Refresh Dev work: each run picks up the latest production data.
Failed runs
If a run fails, the next run is still set up and will run at its next scheduled time. Check the deployment history in the OttoFMS console and set up notifications so you know when a run fails.
Managing a Recurring Deployment
Change the time or frequency
Edit the schedule in the FMS Admin Console under Configuration > Script Schedules. As above, only change the timing and name, not the script or its parameters.
Change what the deployment does
You can't edit a scheduled deployment. To change it:
- Delete the existing scheduled deployment from the OttoFMS console. This also deletes its FileMaker schedule.
- Set up and schedule the updated deployment in OttoDeploy.
- Change the new schedule's frequency in the FMS Admin Console again.
Stop a recurring deployment
Delete the upcoming scheduled deployment from the Deployments page in the OttoFMS console: click the three dots menu and select Delete. This also deletes the FileMaker schedule, so no further runs will happen.
Running two schedules at the same time will cause one of the two to fail. Leave enough time between recurring deployments (and other scheduled deployments) for each one to finish before the next begins.
Was this page helpful?
Refresh Dev
Refresh your development server with the latest production data while preserving in-progress schema changes, without a third staging server.
Low Downtime
Use OttoDeploy's Publish Build option to pre-build and pre-fetch deployments, minimizing file downtime during strict maintenance windows.