Introduction

xx

Rollout Objects and Local Objects

A number of objects suggest to be rolled out across environments without any changes. Most prominently this includes workflows/jobs.

However, a number of objects might be specific for an environment, for example JS7 - Job Resources that hold environment variables that are specific for an environment.

Rollout Objects

JS7 configuration object types that are independent from a specific environment (dev, test, prod) and that can be rolled out across environments include

• Workflows
• Resource Locks
• File Order Sources
• Notice Boards
• Script Includes

Such objects can be managed with JS7 in a way that allows to re-use the objects - without any changes - across rollout environments such as dev, test, prod.

Local Objects

The following configuration object types typically hold values that are specific for an individual environment (dev, test, prod) and therefore usually are added to a separate repository. Such objects are not rolled out across environments.

• Job Resources
• Calendars
• Schedules

Export/Import for Rollout

The JS7 - Inventory Export and Import operations offer a valid strategy to perform rollout operations, for example from dev -> test -> prod environments.

At the same time export/import requires some discipline about the nature of scheduling objects to be local to a specific environment or to be prepared for rollout across environments.

Git Repository Integration for Rollout

The JS7 - Inventory Git Integration offers a number of options for rollout by use of the JS7 - Git Repository Interface.