Automation Platform Tasks

Source control configurations

Use this page to define a new source control configuration (SCM) or modify an existing source control configuration. A configuration is a collection of properties that define how to communicate with a particular source control system.

CloudBees Flow bundles and supports numerous source control types. After creating a source control configuration, your entry will appear in the table on the Source Control Configurations web page— to see this web page, select the Administration > Source Control tab.

Other SCM systems are bundled with CloudBees Flow and available in the Plugin Catalog. Each integration contains options specific to that SCM.

If you need a different SCM not specified in this Help topic, go to the Plugin Manager page to locate your SCM ( Administration > Plugins ). See the Help topic associated with your plugin—located on the Plugins page. At a minimum, you need to enter a name for your configuration, and you may want a minimal text description.

AccuRev

Enter information into the fields as follows:

  • Configuration Name —Type a name for the configuration— any name you choose, but the name must be unique. For example, you might use "myAccuRevServer."

  • Description —You can change or modify the default text description—CloudBees Flow does not use this information.

  • Login As

    • User Name —The name CloudBees Flow needs to use to communicate with your AccuRev system. For example, you may be using a special "read-only" user name similar to "Build" for your user name.

    • Password —The password for the specified User Name.

    • Retype Password —Type the password again.

Click Submit to save your information.

ClearCase

Enter information into the fields as follows:

  • Configuration Name —Type a name for the configuration— any name you choose, but the name must be unique. For example, you might use "myClearCaseServer."

  • Description —You can change or modify the default text description—CloudBees Flow does not use this information.

Click Submit to save your information.

File

You may want to use this configuration with ElectricSentry to "watch" for changes in any files.

Enter information into the fields as follows:

  • Configuration Name —Type a name for the configuration—any name you choose, but the name must be unique.

  • Description —You can change or modify the default text description—CloudBees Flow does not use this information.

Click Submit to save your information.

Git

Enter information into the fields as follows:

Configuration Name —Type a name for the configuration— any name you choose, but the name must be unique.

Description —You can change or modify the default text description—CloudBees Flow does not use this information.

Click Submit to save your information.

Perforce

Enter information into the fields as follows:

Configuration Name —Type a name for the configuration— any name you choose, but the name must be unique. For example, you might use "myPerforceServer."

Description—You can change or modify the default text description—CloudBees Flow does not use this information.

Login As

User Name (P4USER) —The name CloudBees Flow needs to use to communicate with your Perforce system. For example, you may be using a special "read-only" user name similar to "Build" for your user name.

Password (P4PASSWORD) —The password for the specified User Name.

Retype Password —Type the password again.

P4PORT —Sets the hostname and port number ElectricSentry uses to contact the Perforce server ( hostname:1234 ).

P4HOST —The name of the host machine to impersonate.

P4TICKETS —The full path name of the ticket file used by the "p4 login." This value is set as an environment variable, not as a command-line option ( fullPathAndFileName )

P4CHARSET —Sets the character set used for translation of Unicode files ( characterSet )

P4COMMANDCHARSET —Used to support UTF-16 and UTF-32 character sets ( commandCharSet ).

Click Submit to save your information.

Property

You may want to use this configuration with ElectricSentry to "watch" for any property changes.

Enter information into the fields as follows:

Configuration Name —Type a name for the configuration—any name you choose, but the name must be unique.

Description —You can change or modify the default text description—CloudBees Flow does not use this information.

Click Submit to save your information.

Subversion

Enter information into the fields as follows:

Configuration Name —Type a name for the configuration— any name you choose, but the name must be unique. For example, you might use "mySubversionServer."

Description —You can change or modify the default text description—CloudBees Flow does not use this information.

Login As

User Name —This is the name CloudBees Flow needs to use to communicate with your Subversion system. For example, you may be using a special "read-only" user name similar to "Build" for your user name.

Password —This is the password for the specified User Name.

Retype Password —Type the password again.

Click Submit to save your information.

Checking out code from a source control system

Go to Projects > select a project > select a procedure. To create a New Step for source code management, select the Plugin link.

  • In the Choose Step panel, select Source Code Management from the left pane, then select the SCM you configured.

  • The right-pane now shows the types of steps available for your configuration. Select the step you need and automatically go to the New Step page.

  • On the New Step page, notice the Subprocedure section now contains the SCM integration you configured and the step you chose.

  • Enter the remaining information to create your SCM step.

To edit an existing source control configuration

Modify any of your source control configuration information by re-entering any previously entered information. Click Submit to save your modified source control information.