Skip to content

Add Salt 3008 test coverage, driven off generate.py's version list#67

Merged
twangboy merged 4 commits into
saltstack:mainfrom
twangboy:add_3008_tests
Jul 9, 2026
Merged

Add Salt 3008 test coverage, driven off generate.py's version list#67
twangboy merged 4 commits into
saltstack:mainfrom
twangboy:add_3008_tests

Conversation

@twangboy

@twangboy twangboy commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

What does this PR do?

Add 3008/3008.1 to generate.py's SALT_VERSIONS/VERSION_DISPLAY_NAMES and make it the single source of truth the test suites query (via new --print-versions/--print-upgrade-steps CLI modes), instead of hand-writing a new file or block per Salt major. The CI matrix now also derives one upgrade- job per adjacent major pair, so future majors (3009, ...) only require a one-line edit to SALT_VERSIONS.

  • Windows: test_install_major.ps1, test_install_exact_ver.ps1, and test_upgrade.ps1 read $SALT_TEST_VERSION (set from matrix.instance) to test only their assigned version/step, or loop over everything when run locally without it.
  • Linux: test-linux.sh gains the same data-driven major/exact/upgrade checks, sourced from the real network (no new testarea binaries), and drops the stale "no 3008 GA yet" stub.

twangboy added 4 commits July 9, 2026 11:19
Add 3008/3008.1 to generate.py's SALT_VERSIONS/VERSION_DISPLAY_NAMES and
make it the single source of truth the test suites query (via new
--print-versions/--print-upgrade-steps CLI modes), instead of hand-writing
a new file or block per Salt major. The CI matrix now also derives one
upgrade-<major> job per adjacent major pair, so future majors (3009, ...)
only require a one-line edit to SALT_VERSIONS.

- Windows: test_install_major.ps1, test_install_exact_ver.ps1, and
  test_upgrade.ps1 read $SALT_TEST_VERSION (set from matrix.instance) to
  test only their assigned version/step, or loop over everything when run
  locally without it.
- Linux: test-linux.sh gains the same data-driven major/exact/upgrade
  checks, sourced from the real network (no new testarea binaries), and
  drops the stale "no 3008 GA yet" stub.
Keep a thin version check before the upgrade, but run the same
status/binaries/service/config/ping/version battery Windows already
runs after the upgrade, since that's the state that actually matters
and it exercises the stop-old/start-new service transition that a
fresh install never does.
Lets the full test suite (all versions, all jobs) be triggered
on-demand from the Actions UI/gh CLI, or automatically once a week,
without needing a PR to exercise the changed-files gate.
Drop binaries-present, PATH, and ping checks from the post-upgrade
battery on both platforms - those are generic install checks already
covered by the major/exact-version jobs. Keep status, service
running, config preservation, and version bump, since those are the
only things that actually exercise upgrade-specific behavior
(stop-old/start-new transition, config carried forward). Cuts
unnecessary work per upgrade CI job.
@twangboy twangboy merged commit 59fa065 into saltstack:main Jul 9, 2026
20 checks passed
@twangboy twangboy deleted the add_3008_tests branch July 9, 2026 19:59
@twangboy twangboy added the bug Something isn't working label Jul 9, 2026
@twangboy twangboy self-assigned this Jul 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant