Creating components from Subversion

Subversion is a source-code management system.

Before you begin

Install the Subversion client on the IBM® UrbanCode Deploy server. For example, on Linux, you can use the package manager to install Subversion with a command that is similar to these examples:
yum install subversion
apt-get install subversion
zypper install subversion

Procedure

  1. In IBM UrbanCode Deploy, click Components, and then click Create New Component.
  2. In the Create New Component window, specify a name and description for the component.
  3. In the Teams fields, specify the access information for the new component.
  4. 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.
  5. In the Source Config Type list, select Rational Asset Manager..
  6. Specify the following parameters for the component:
    Repository URL
    The location of the Subversion repository, such as
    http://svn.mycompany.com/svn/myrepository
    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.
    User
    The user name for the repository.
    Password
    The password for the repository.
    SVN Path
    The path to the svn executable file on the IBM UrbanCode Deploy server. If you added the executable file to the system PATH variable, you can specify the name of the executable file, such as svn. If you have not added the executable file to the system PATH variable, specify the complete path, such as /usr/bin/svn.
    Preserve Execute Permissions
    For Linux and UNIX operating systems, select this check box to retain the execute permissions for each file.
    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 > [component] > Versions and then clicking Import New Versions.
    Copy to CodeStation
    This option, which is selected by default, creates a tamper-protected copy 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.
    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.
    Inherit Cleanup Settings
    Specify how many component versions to keep in CodeStation, and how long to keep them. If you select this check box, the component uses the values that are specified on the System Settings pane. If you clear this check box, the Days to Keep Versions (initially set to -1, keep indefinitely) and Number of Versions to Keep (initially set to -1, keep all) fields are displayed, and you can define custom values.
    Run process after creating a new version
    To automatically run a process after each new version is created, select this check box and then specify an application process and an environment for the process.
  7. Click Save.

Results

The new component is listed on the Components page. The Versions tab shows the versions of the component that are available. If you selected the Import Versions Automatically check box, versions are displayed automatically. Otherwise, click Import New Versions to show the available versions. Depending on the number and size of the artifacts, it might take time before the versions are displayed. To see the artifacts in the component, click a component version.

What to do next

Create processes for the component. See Configuring component processes.

Feedback