To import artifacts that are not stored in versioned folders,
store the artifacts in a folder and create a component with the File
System (Basic) source configuration type.
About this task
When you use this type of component, you must manually create
versions. To create versions of components automatically, see
Creating components from a versioned file system.
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 File System (Basic).
- Specify the following parameters for the component:
- Base Path
- Specify the path to the directory that contains the artifacts.
- Always Use Name Pattern
- If you select this check box, new versions are automatically named
according to the pattern in the Version Name Pattern field.
If you clear this check box, you must specify a name each time you
create a version.
- Version Name Pattern
- Specify a pattern for each version name. You can use the ${version} variable
to include an automatically incremented version number. For example,
the mycomp_${version} pattern produces versions such
as mycomp_1, mycomp_2, and so on.
This
parameter is meaningful only if you select the Always Use
Name Pattern check box.
- Next Version Number
- Specify the version number for the next version.
This parameter
is meaningful only if you select the Always Use Name Pattern check
box.
- Preserve Execute Permissions
- For Linux and UNIX operating systems, select this check box
to retain the execute permissions for each file.
- Import Versions Automatically
- This parameter has no effect on this source configuration type.
You must import new versions manually.
- 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. The
new component appears in the list of components.
- Import the first version of the component:
- Go to the Versions tab.
- Click Import New Versions.
- Specify a name for the new version and then click Save.
The new version appears in the list of versions. You can
confirm that the artifacts are included in the version by clicking
the version and looking at the list of artifacts.
- To import future versions of the component, click Import
New Versions again and specify a name for the new version.
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.