Configure One Agents for importing component versions

Each time a component's artifacts are imported into the repository, including the first time, it is versioned.

Versions can be assigned using

1. Automatically by IBM® UrbanCode Deploy,
   
2. Applied manually, or
   
3. Come from a build server.
   

A version can be

1. Full - A full version contains all component artifacts
   
2. Incremental - an incremental version contains only the artifacts that are different from the previous version.

Every time a component's artifacts are modified and reimported, a new version of the component is created. So a component might have several versions in CodeStation and each version is unique.

How to configure agents for component versions?

On the computer where you installed the agent, add files that represent deployable artifacts to the file system.

1. Create a directory and give it a name such as helloWorld on the file system where the agent is located.
2. In the helloWorld directory, create a subdirectory that is named 1.0. The source configuration the tutorial uses treats each subdirectory in the target directory as a different component version.
3. In the 1.0 directory, place several files with any name and extension. The files represent the artifacts that the agent deploys by using the processes that you create.

Where Component versions are stored?
Component versions must be designated to one agent for importing versions. By default, one system-wide agent is designated to import component versions. To designate the agent, see uDeploy server "settings" and "Agent for Version Imports". For more info.
system-wide-settings-udeploy-server.html

Tracking environment inventory for components
You can track the environment inventory for each component by clicking the component and then going to the Usage tab.

Importing versions manually
Display the Version pane for the component you want to use (Components > selected component > Versions). Click Import New Versions. The new version or versions appear in the table of versions.

Cleaning up component versions
You can configure the server to reduce the number of component versions by archiving them. You can specify global cleanup settings, cleanup settings for individual components, and cleanup settings for specific environments. When archiving versions, the server retrieves the settings from the Settings > System Settings > Artifact Cleanup options first.

Deleting versions
If you want to archive deleted versions, click Settings > System Settings and in the Archive Path field, specify a folder location for archived versions. Then, click Save. To delete a version, use the Delete action for the version: click Components > selected component > Versions > selected version > Delete. Deleting a version removes the artifacts from CodeStation and the component version from the list of versions.