AntHillPro is a build integration tool.
Before you begin
Install an agent that has access to the AntHillPro server.
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
AntHillPro.
- Specify the following parameters for the component:
- Anthill URL
- The URL of the AntHillPro server.
- User
- The user name of the AntHillPro-credentialed user.
- Password
- The password of the AntHillPro-credentialed user.
- Project
- The name of the project. AntHillPro projects roughly correspond to IBM UrbanCode Deploy
components.
- Workflow
- The name of the workflow that contains the AntHillPro builds to import.
- Status
- The status that a build life must have before it can be imported. Only build lives with this
status are imported.
- Artifact Sets
- If Copy to CodeStation is checked, type the list of artifact sets that
will be resolved in CodeStation. Place each list item on a new line.
- 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.
- 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 in the
System Settings page is used to import component artifacts.
Agents must have access to the system where the artifacts are located. 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
- 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, which means keep indefinitely) and Number of
Versions to Keep (initially set to -1, which means
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 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 available versions of the component. 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.