Software configuration management overview

As you develop workflows, especially if multiple developers are working on different parts of the same workflow, you might want to use an external software configuration management (SCM) system to track the changes. With an SCM, you can reconcile different versions, revert to previous versions, and more.

When you use an SCM with the TrueSight Orchestration Development Studio application, you can determine the status of your work relative to the shared SCM repository and if a workflow is newly created, locally modified, or has conflicting changes relative to the state of the shared SCM repository.

You can integrate TrueSight Orchestration Development Studio with the following SCM systems:

  • CVS
  • GitHub
  • Perforce
  • Subversion

You must have one of the supported SCM systems installed and configured before you can configure TrueSight Orchestration Development Studio to use the SCM system.

Note

The integration with external SCM systems is provided through third-party plug-ins. Not all the features are supported. Some features may not work as expected.

The TrueSight Orchestration Development Studio to SCM system relationship is defined at the grid level. If you are using an SCM system, all the modules in any one grid must be managed with the same SCM system. You can configure other grids to use different SCM systems.

Related topic

Developing-workflows

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*