Epic Goal

Empower customers to use the persistent volumes feature of Shipwright in their builds.

Why is this important?

Persistent volumes for builds was adopted in an earlier release of Shipwright. However its application has not been fully documented.

Scenarios

1. Cache container image layers between builds
2. Cache language dependencies between builds (maven, node_modules, etc.)

Acceptance Criteria (Mandatory)

• Customers can use the persistent volumes feature of Shipwright by following instructions in our documentation
• Customers can see the persistent volumes feature in action through a video demonstration
• CI verifies any instructions/procedures in the documentation work as expected.
• Common error scenarios are documented and provide known solutions/steps to fix.

Dependencies (internal and external)

1. Standalone builds for OpenShift docs

Previous Work (Optional):

1. BUILD-9: Shipwright Build strategy Volumes

Open questions::

• TBD

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment