DevOps

Because a job repository is simply a directory on the file-system, it lends itself easily to managing through a version control system like tfs or git. At the same time it is easy to migrate jobs to another environment by copying either directly or through your the version control system.

Here are some guidelines for effectively setting up your environment:

• Check your job-directory in source-control. Do not check in your executions directory.
• Create a separate repository to house environment-specific files. This repository should not be checked in to source control.
• Create a separate repository to house schedules. Schedules are often different between environments, so it makes more sense to set them up for each environment separately.
• If this is an option for you, you can store your Tasxs-jobs in the same repository as other project-related artifacts, such as ETL-jobs. That way configuration-changes to the jobs can be kept synchronized with other changes.