How Lockstep fits into your pipeline

Lockstep, formerly artifactz.io, is the gatekeeper for your promotion pipeline. We built it to track software versions in complex pipelines and to make sure that a version can only move to the next environment once it has been registered and validated in the one before. It records which version of every artifact belongs to every stage, and it works alongside the CI/CD, registry and deployment tools you already use.


Use Cases

Controlling artifact versions with Lockstep brings no skipped stages, no accidental releases and a clear answer to "which version is running where?". Here are two use cases where Lockstep helps you be more efficient:

Docker Images

Suppose you want to run integration tests that include other product images built in the same way. Which image versions should the integration test stack use? Using the latest image tag is not the best practice, but you can associate a specific version of the Docker image with each testing or production stage in Lockstep. This way, you have full control over what gets deployed by the testing pipeline.

Java Libraries

For a complex Java product that has several dependencies, how can you ensure the correct versions of these dependencies are used? Declare a specific stage and associate the library version with it in Lockstep. Then use the Gradle plugin to automatically resolve dependencies during build or assembly.

Terminology

Artifact - the Docker image or Java library whose versions are tracked by Lockstep. Lockstep stores references to versions, not the artifacts themselves.

Stage - the state of the system associated with the specific phase of its lifecycle, such as Development, User Acceptance Testing, or Production.

Promotion - moving a version from one stage of its flow to the next, one stage at a time, once it has been validated in the current one.

Flow - the sequence of stages through which an artifact travels during its lifecycle. If an Artifact is linked to the flow, a new version can only be added to the first stage of the flow. After that, the version can only be pushed through the flow.

This website uses cookies. By continuing to browse this site, you agree to this use.