Components and Versions

Note

• Components are code repositories that wrap tools, see Components
• Components come with Versions that correspond to tags in the github repository
• When Component Versions are added then the odtp.yml is parsed: it needs to conform to the standards described at odtp.yml format
• The building blocks in ODTP are Component Versions
• Component Versions can also be added via the Commandline

Manage Component Versions

In the Dashboard you can list all Component Versions that are already on ODTP.

• you can deprecate Component Versions
• you can also reactivate them
• you can chose to also show deprecated Component Versions. By default they are not displayed

Add a new component version

In order to start using the components in ODTP you need to add them to the platform. Components are the building block in workflows and executions.

• Components are imported by their github url and Version correspond to the version tags.
• A component repository should have a valid tag in order to be imported.
• A component version also needs to have a valid odtp.yml. Otherwise it can not be imported into ODTP: see odtp.yml specification

Under the tab "Add Component Version" you can either add a new component with a component version or a new version for an existing component.

You will see a message when ODTP was able to parse the odtp.yml file

Error case: odtp.yml file could not be parsed:

Component Version Details

The component version gets the default configuration and other metadata from the odtp.yml file: you can see this information in the detail tab:

Next add Workflow

Once you have added all the component versions you need, you can combine them into Workflows:

Workflows