ci: add juju 4/beta to integration test matrix#166
Merged
Conversation
Copilot
AI
changed the title
[WIP] Update workflow to expand matrix strategy for juju-channel
ci: add juju 4/beta to integration test matrix
Dec 10, 2025
sed-i
approved these changes
Dec 10, 2025
cab929b to
9ded678
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue
The
_integration.ymlworkflow only tests with Juju3.6/stable. We need coverage for4/betachannel, but only for thetls_fullscenario to avoid excessive test runtime.Solution
Vectorized the matrix strategy to include
juju-channeldimension:juju-channel: ["3.6/stable", "4/beta"]to matrixexcludeto restrict4/betatotls_fullscenario only3.6/stablereferences with${{ matrix.juju-channel }}Result: 5 test combinations (4 scenarios × 3.6/stable + 1 scenario × 4/beta) instead of 4.
Checklist
Context
GitHub Actions matrix exclusions allow selective test coverage without duplicating job definitions. The
excludekey removes specific combinations from the cartesian product.Testing Instructions
Trigger the workflow and verify:
4/betaruns only withtls_full3.6/stableruns with all 4 scenariosUpgrade Notes
No upgrade impact. This is a CI-only change.
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
canonical-bos01.cdn.snapcraftcontent.com/usr/lib/snapd/snapd /usr/lib/snapd/snapd(dns block)If you need me to access, download, or install something from one of these locations, you can either:
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.