Creating components from Git

Git is a source-code management system.

1. In Deploy, click Components, and then click Create Component.
   The Create Component window displays.
2. To use a template for the new component, select a template from the Template list.
   In this case, the component inherits source configuration, properties, and processes from the template. For information about templates, see Component templates.
3. Specify a name and description for the component.
4. In the Teams fields, specify the access information for the new component.
5. In the Source Configuration Type list, select Git.
6. Specify the following parameters for the component:

   Repository URL

   The location of the Git repository, such as https://git.example.com/myproject.git.

   Branch

   The name of the branch to use.

   User Name

   The user name to authenticate with the Git repository if using HTTPS protocol.

   Password

   The password to authenticate with the Git repository if using HTTPS protocol. You can also use the Git Personal Access Token (PAT) if the PAT is defined in the key-value store of the Vault.

   Watch for tags

   Select this check box to use tags as the basis for new component versions.

   Includes

   A list of file patterns to include in the component. Separate each pattern with a carriage return.

   Excludes

   A list of file patterns to exclude from the component. Separate each pattern with a carriage return.

   GIT Path

   The path to the Git executable file on the Deploy server. If you added the Git executable to the system PATH variable, you can specify the name of the executable, such as git. If you did not add the Git executable to the system PATH variable, specify the complete path to the Git executable, such as /usr/bin/git.

   Preserve Execute Permissions

   For Linux® and UNIX operating systems, select this check box to retain the execute permissions for each file.

   Extensions of files to Convert

   If text-type files must be converted into another character set, type the list of file extensions to be converted. Matching file types are converted into the default or system character set of the system where the agent is located. Separate list items with commas, for example:

   txt,log,ini,sh

   Import Versions Automatically

   Select this check box to check for new versions periodically and to import new versions automatically. If you do not import versions automatically, you can import versions manually by clicking Components > selected component > Versions and then clicking Import New Versions.

   Copy to CodeStation

   This option, which is selected by default, creates tamper-protected copies of the artifacts and stores them in the embedded artifact management system, CodeStation. If the check box is cleared, only metadata about the artifacts is imported. In most cases, keep this check box selected. The default for this setting is in the system setting Components copy to CodeStation by default. For more information, see System settings.

   Default Version Type

   Specify how to import versions into CodeStation:

   Full

   Each version is comprehensive and contains all artifacts.

   Incremental

   Each version contains a subset of artifacts.

   Use the system's default version import agent/tag

   If this parameter is selected, the agent or tag that you specified on the System Settings page is used to import component artifacts. Agents must have access to the system where the artifacts are located. For more information, see System settings.

   Import new component versions using a single agent

   If this parameter is selected, use the Agent for Version Imports field to identify the agent that is used to import artifacts into the component. The agent must have access to the system where the artifacts are located. To import artifacts from where the server is located, install an agent in the same location and specify that agent.

   Import new component versions using any agent with the specified tag

   If this parameter is selected, use the Agent Tag for Version Imports field to identify the tag that is used to select agents to import artifacts into the component. All tagged agents must have access to the system where the artifacts are located.

   Inherit Cleanup Settings

   To apply the component version cleanup settings that are specified on the System Settings page, select the Inherit Cleanup Settings check box. If this check box is cleared, you must specify how long to keep component versions. For more information about cleaning up component versions, see Cleaning up component versions.

7. Click Save.