Git is a source-code management system.
Before you begin
Install Git on the
IBM® UrbanCode Deploy server.
When you create the component, you must specify the path to the Git
executable file.
Procedure
- In IBM UrbanCode Deploy,
click Components, and then click Create
New Component.
- In the Create New Component window,
specify a name and description for the component.
- In the Teams fields,
specify the access information for the new component.
- 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.
- In the Source Config Type list,
select Git.
- Specify the following parameters for the component:
- Repository URL
- The location of the Git repository, such as https://git.mycompany.com/myproject.git.
- Branch
- The name of the branch to use.
- 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 IBM UrbanCode Deploy server.
If you have added the Git executable to the system PATH variable,
you can simply specify the name of the executable, such as git.
If you have not added 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.
- 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 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.
- 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.