---
title: "2026-09-16 Gleason branch image testing"
description: "PR 339 can be tested with a branch image before merging."
image: "https://docs.virdx.dev/img/virdx-social-card.png"
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.virdx.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# 2026-09-16 Gleason branch image testing

## Work Done

Reviewed the prior conversation and [histo PR 339](https://github.com/virdx/histo/pull/339). Both Argo steps use the supplied image_tag without a main-only constraint. Dockerfile.argo includes scripts and configs. Build the branch with kuberun build, submit with its returned tag, then use a pinned main-<sha> image after merge. No build, workflow submission, or histo edits performed.

## Pitfalls

The prototype comment and previous advice incorrectly presented merging as a prerequisite for testing. Image contents, not branch name, are the requirement. Data publication, credentials, HF access, and runtime validation remain separate prerequisites; their live status was not checked.

## Improvements

Document branch-image smoke testing separately from production main-image use. The current workflow writes to production vxData and ClearML; branch testing is not a sandbox.

Source: https://docs.virdx.dev/knowledge/inbox/2026-09-16-histo-gleason-branch-image-testing/index.mdx