UrbanCode Deploy

Moving Codestation to S3

Version 7.0.5.0 of UrbanCode Deploy includes a few solutions that aim to address the growing storage footprint that comes with extended usage of the Deliver server. The two areas that will see the most growth over time are the versioned database tables used to preserve information about past deployments should they ever need to be reviewed in an audit, and the collection of build artifacts stored locally in the Codestation artifact repository.

Versioned database record growth has been mitigated by <link> Compressing Versioned Configuration Records </link>. With version 7.0.5.0, we’ve introduced the ability to store build artifacts in an S3 bucket.

Any cloud storage solution that implements the S3 specification is compatible for artifact storage. Once a UCD server is configured to store artifacts in an S3 bucket, it will no longer look at the local codestation repository for version artifacts – it will only retrieve artifacts from the bucket.

There are two scenarios to consider when configuring the UCD server to use an S3 bucket: configuring a fresh instance that has not yet imported any artifacts, and migrating previously imported version artifacts from an existing Deliver server into S3.

The migration scenario is described in this documentation. Migrating many build artifacts to S3 will take time, so we provided an S3 Migrator tool in the Tools section of UCD that will upload artifacts while the UCD server is running. We recommend that the S3 migrator tool is run multiple times until the time it takes to upload new artifacts to the S3 bucket can fit in a single downtime window.

Configuring S3 Codestation on a fresh UCD instance is as simple as following step 4 in the previously mentioned documentation. Not all properties defined need to be added to the server’s installed.properties file, since it depends on how the S3 bucket is configured. Work with your S3 provider to determine what parameters are relevant.

 

Tags:

codestation
Deploy
UrbanCode Deploy