Creating components from ClearCase
ClearCase is a source-code management system.
Before you begin
Procedure
-
In Deploy,
click Components, and then click Create
Component.
The Create Component window displays.
- 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.
- Specify a name and description for the component.
- In the Teams fields, specify the access information for the new component.
- In the Source Configuration Type list, select ClearCase.
- Specify the following parameters for the component:
- Path to location inside the View
- The location of the base directory on the IBM® Rational® ClearCase® server from which files are imported.
- 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.
- Snapshot View
- Check this box if the connection is a snapshot view.
- Clear Tool Path
- If the
cleartoolfile is not on the path variable, type the location of thecleartoolexecutable file. - 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 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.
- Click Save.