In my last post there’s a tidbit about overcoming an access problem using an agent (or the CLI). That was with UCD 6.0. No need for this with the upcoming release of UCD 6.0.1 : see Eric Minick’s post about Plugins for Artifact Sources.
So as in my post an agent is installed on the packaging server but instead of having to define a process using the Create Versions step, simply configure the component to use this agent to run the appropriate Source Config type. Here’s look at the new configuration settings:
Selecting this means the Agent or Agents specified in Settings > System > System Settings will be used. Either a specific agent or a group of agents with a tag can be specified here.
Option 2: Import new component versions using a single agent
Specify a single agent to always use for this component rather than the Agent(s) specified in the System Settings.
Specify an Agent or Agents with a specific tag to always use for this component rather than the Agent(s) specified in the System Settings.
How often an agent checks for new versions to import is specified in the “Automatic Version Import Check Period” System Setting. Or a manual import can be initiated using “Import New Versions”
There is now an additional section in the Versions tab for Components that shows if there are any currently executing imports, which can be cancelled if required.
The import history for a component can be viewed its Configuration tab.
Now since the source configs are implemented as plugins, implementing a custom importer that, for example, constructs custom version names or imports bits and pieces from a complex directory structure, is as simple as writing a new plugin.