Deploying Script Versions
Theme: Build
Who Is It For? System Administrator, Automation Engineer
What Is It?
The Deploy Version feature deploys a specific script version to all or a subset of Master jobs already associated with that script. For example, if "Version 3" is associated with ten jobs across ten schedules, the deployment wizard can replace it with "Version 7" across all those jobs at once.
To deploy a script version, complete the following steps:
- Select on Repository under the Scripts topic
- Select a script in the list
- Select the Show/Create Versions button on the toolbar
- Select the script version to deploy
- Select the Deploy button. The Deploy Version dialog displays
- (Optional) Enter a schedule or job name to filter the list of available jobs
- Select the jobs to redeploy the script version to
- Select the Deploy button in the Deploy Version dialog
- Select Yes to confirm the deployment
- Select Yes again to redeploy to additional jobs and repeat Steps 6–8, or select No to proceed
- Select the Close button in the Versions dialog
- Select Close ☒ to close the Script Repository screen
FAQs
Q: How many steps does the Deploying Script Versions procedure involve?
The Deploying Script Versions procedure involves 12 steps. Complete all steps in order and save your changes.
Glossary
Schedule: A named container for jobs in OpCon, built for a specific date to create that day's automation. Schedules define build settings, frequencies, and the jobs that run within them.
Job: The fundamental unit of work in OpCon. A job defines what to run, on which machine, when to start, and what conditions must be met. Job results are tracked and can trigger events and notifications.