[DPE-4976] Add workflow for nightly scheduled tests with juju 3.6 #502
Conversation
…ith consistent approach
|
All juju 3.6 tests pass in https://github.com/canonical/mysql-operator/actions/runs/10460916031/ which is the run for commit hash 4c7ba8e |
|
All juju 2.9.49 and 3.4.4 tests pass in https://github.com/canonical/mysql-operator/actions/runs/10472342308 |
shayancanonical
requested review from
paulomach,
taurus-forever and
carlcsaposs-canonical
.github/workflows/juju_3_6_ci.yaml
Outdated
| cloud: lxd | ||
| juju-snap-channel: 3.6/beta | ||
| libjuju-version-constraint: 3.5.2.0 | ||
| lxd-snap-channel: 5.21/stable |
There was a problem hiding this comment.
IMHO, we should use here LXD latest/stable: v.6.1.
Reasons: Field will deploy Juju LTS with latest stable LXD.
Also, please pin MicroK8s here with renovate refresh label as discussed in MM.
There was a problem hiding this comment.
will add a renovate refresh label for lxd in a separate PR once a preset for lxd has been created.
do we want to use latest/stable: v6.1 for all juju versions?
|
@taurus-forever do you want 3.6 on amd64 only, arm64 only, or both? |
.github/workflows/ci.yaml
Outdated
| libjuju-version-constraint: ${{ matrix.juju.libjuju }} | ||
| lxd-snap-channel: 5.21/stable | ||
| lxd-snap-channel: ${{ matrix.lxd_channel || '5.21/stable' }} |
There was a problem hiding this comment.
can we use same lxd channel for all runs?
There was a problem hiding this comment.
running all tests with lxd 6.1/stable in 0f57e9a. please confirm that this is alright @taurus-forever
Issue
We would like to run nightly tests with juju 3.6
Solution
Upgrade to dpw v21.0.0 and add juju 3.6 into the matrix for tests. Also, upgrade libjuju to
^3.5.2.0