Introduction → Elements of Deployment Automation → Components → Importing Component Versions
After defining a component's source and processes, you import its artifacts into Deployment Automation's artifact repository, CodeStation. Artifacts can be imported automatically or manually.
By default, a complete copy of an artifact's content is imported into CodeStation. The original artifacts are untouched. This provides tamper-proof storage and the ability to review and validate artifacts with the Serena Deployment Automation user interface. If you have storage concerns or use a tool like Maven, you can limit CodeStation to using references to the artifacts instead of actually copying them.
Each time a component is imported, including the first time, it is versioned. Versions can be assigned automatically by Deployment Automation, applied manually, or come from a build server. Every time a component's artifacts are modified and re-imported, a new version of the component is created.
A component may have several unique versions in CodeStation. A version can be full or incremental. A full version contains all component artifacts; an incremental version contains only the artifacts modified since the previous version was created.
Copyright © 2011–2015 Serena Software, Inc. All rights reserved.