bump-image

Update LiftWing Docker image tags in Helm values.yaml files.

4|Updated May 12, 2021
One-click install
npx skills add https://github.com/wikimedia/machinelearning-liftwing-inference-services --skill bump-image
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bump-image
Source: https://github.com/wikimedia/machinelearning-liftwing-inference-services/tree/main/.claude/skills/bump-image
Command: npx skills add https://github.com/wikimedia/machinelearning-liftwing-inference-services --skill bump-image

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents deployment mismatches by helping you update the correct Helm values files to match a newly published LiftWing inference-service Docker image tag.

Core Features & Use Cases

  • Pull published image tags from Gerrit: Uses PipelineBot messages for the specified inference-services CL to discover which image tags were published.
  • Select the right inference services automatically: Pre-filters candidate services by correlating changed model directories with the discovered image names, and optionally narrows further with explicit isvc-name arguments.
  • Edit only the image tag in deployment charts: Updates the specific old tag strings to the new tag in the appropriate values.yaml files without changing other YAML keys.
  • Draft a deployment-ready commit message: Produces a Wikimedia-convention commit message using the extracted Bug trailer, without running git commit automatically.

Quick Start

Ask an AI to run bump-image for a merged inference-services CL and update the matching LiftWing deployments: provide the CL number and optional isvc names, then review the drafted commit message and apply it.

Frequently Asked Questions about bump-image

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update Docker image tags in Helm values.yaml files for a new deployment?

To update Docker image tags in Helm values.yaml files, you replace specific old tag strings with the new tag in the appropriate values.yaml files without altering other YAML keys. This prevents deployment mismatches by matching Helm charts to newly published Docker images.

How do I get published Docker image tags from a Gerrit changelist for Kubernetes deployments?

You can get published Docker image tags from a Gerrit changelist by reading PipelineBot messages posted on the specified inference-services CL. These messages contain the references needed to discover which image tags were successfully published by Jenkins.

Can I automatically select which inference services to update when bumping image tags?

Yes, you can automatically select inference services by correlating changed model directories with the discovered image names. You can also optionally narrow the selection further by providing explicit inference service name arguments to target specific deployments.

Does bumping Helm chart image tags generate a git commit message automatically?

Bumping Helm chart image tags drafts a Wikimedia-convention git commit message that includes the extracted Bug trailer, but it does not run git commit automatically. You must review the drafted message and apply the commit manually.

What is the best way to avoid deployment mismatches when updating LiftWing service images?

The best way to avoid deployment mismatches is to update the correct Helm values files to match a newly published LiftWing inference-service Docker image tag. This ensures operations/deployment-charts accurately reference the latest Jenkins-published images.