bdd-container-update
Update the BDD test container image when its dependencies or runtime change. Determines version bump (major vs minor vs patch), rebuilds the Docker image, pushes to GitLab registry, and updates the image tag in start_test.sh. Test source (tests/, features/, scripts/, data/, conftest.py) is bind-mounted from the host repo at runtime, so pure test code changes do NOT require a container rebuild. Use only when files that the container bakes in are
npx skills add NVIDIA-AI-Blueprints/video-search-and-summarization --skill bdd-container-update --agent cursor
Same command for any agent — swap --agent for claude-code, codex, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# BDD Test Container Update The BDD test container runs `bdd_test` from `<INTERNAL_REGISTRY>/bdd_tests:<TAG>`. Since the CI runner bind-mounts the host repo's test source into `/app/`, the image only needs to be rebuilt when the things it bakes in change. ## When to rebuild **Rebuild required** -- files baked into the image: - `test/bdd_tests/Dockerfile` - `test/bdd_tests/docker-entrypoint.sh` - `test/bdd_tests/pyproject.toml` (any change -- deps or pytest config) - `test/bdd_tests/poetry.lock` **Rebuild NOT required** -- bind-mounted at runtime by `cicd_files/docker-compose-test/start_test.sh`: - `test/bdd_tests/tests/**` - `test/bdd_tests/features/**` - `test/bdd_tests/scripts/**` - `test/bdd_tests/data/**` - `test/bdd_tests/conftest.py` - `test/bdd_tests/config.json` If a change touches only files in the second list, stop here -- no container work is needed and `start_test.sh` is unchanged. ## 1. Identify the current image tag The image tag lives in `cicd_files/docker-compose-test/start_test.sh` inside the `update_docker_compose()` function, on the line that sets the `test` service image: ``` image: <INTERNAL_REGISTRY>/bdd_tests:v<MAJOR>.<MINOR>.<PATCH>_x86 ``` Extract the curre
- When to rebuild
- 1. Identify the current image tag
- 2. Determine version bump
- 3. Build the new container image
- 4. Push to GitLab registry
- 5. Update the image tag in starttest.sh
- 6. Summary
- Quick reference
cd test/bdd_tests docker build -t <INTERNAL_REGISTRY>/bdd_tests:v<NEW_VERSION>_x86 . docker push <INTERNAL_REGISTRY>/bdd_tests:v<NEW_VERSION>_x86 docker login <INTERNAL_REGISTRY>
What does the bdd-container-update skill do?
Update the BDD test container image when its dependencies or runtime change. Determines version bump (major vs minor vs patch), rebuilds the Docker image, pushes to GitLab registry, and updates the image tag in start_test.sh. Test source (tests/, features/, scripts/, data/, conftest.py) is bind-mounted from the host repo at runtime, so pure test code changes do NOT require a container rebuild. Use only when files that the container bakes in are
How do I install it?
Run `npx skills add NVIDIA-AI-Blueprints/video-search-and-summarization --skill bdd-container-update --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From NVIDIA-AI-Blueprints/video-search-and-summarization, a repository with 1,773 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.