Add upgrade tests that pin versions

Open
#2,632 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
devops, testing

Research direction

Start by reviewing the existing upgrade test cases and the representative cases linked from bootc PR 2629. Identify how the suite builds images and covers both ostree and composefs, then add a scheduled case starting from a pinned older bootc tag. Done means the extended suite exercises both filesystems; image-builder and Anaconda installs are follow-up goals.

Written by the indexing model from the issue text.

Description

We should have extended upgrade tests that actually pin bootc versions. Right now our upgrade tests "float". Let's add a distinct case that covers upgrades from an older bootc.

Implementing this would be a scheduled job that builds images starting from e.g. latest centos-stream10 but explicitly builds from a pinned bootc tag. I think we can generate a representative set of those starting from the cases in https://github.com/bootc-dev/bootc/pull/2629

This extended suite MUST also cover both ostree and composefs as we have today.

For now this will primarily be bcvk to-disk based but I do want to handle image-builder and Anaconda based installs ideally as a followup, so at least prepare for that.

Dominant language
Rust
Stars
2.3k
Forks
230
Avg merge
2d 11h
Merged PRs (30d)
42

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bootc-dev/bootc

All issues in bootc-dev/bootc

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.