Artifact Tracking in Software Value Streams

Written by: Karan Malhi
2 min read

Software value streams track value flowing from idea to production. This requires that you have the ability to track each piece of value accurately. In CloudBees DevOptics Value Streams, we provide this ability via tracking tickets and code commits which are embedded in packaged artifacts like WAR/JAR files, Docker images, RPM Package Manager files and so on. We perform this tracking via fingerprinting such artifacts.

We however soon discovered some limitations in fingerprinting, namely:

  • Fingerprinting lacks information on whether a value stream gate is producing an artifact or consuming an artifact from an upstream gate.

  • You need workarounds and hacks to fingerprint and track Docker images, Amazon Machine Images (AMIs) and RPM files.

  • Tracking artifacts across Jenkins controllers was extremely difficult.

Introducing Value Stream Artifact Tracking

CloudBees DevOptics Value Stream Artifact Tracking now provides an easy and more reliable method to track artifacts. You can now specify which value stream gates produce and consume artifacts. It addresses all the shortcomings of fingerprinting listed above and gives you the ability to track any type of artifact across Jenkins controllers.

You have the flexibility of using it within Jenkins pipelines or freestyle Jenkins jobs. The usage is even simpler when using the withMaven pipeline step.

Detailed documentation with examples can be found here

Use CloudBees DevOptics Free

If you’re not already using DevOptics, I encourage you to register and get a free for life access to CloudBees DevOptics CD Platform Monitoring . To get access to the value streams functionality and get a demo, click here .

Stay up to date

We'll never share your email address and you can opt out at any time, we promise.