Skip to content

Commit

Permalink
ci: only update ops, not all dependencies (#1275)
Browse files Browse the repository at this point in the history
When running `poetry lock` in the CI workloads, only update the ops
dependency, not all dependencies. We want to know whether the proposed
changes to ops would break the charm's tests, not whether updating all
dependencies, including the proposed ops changes, would do so.

This is one of the suggestions in #1272. Using `poetry add --lock` seems
slightly cleaner than the `sed` system we currently use, but I wasn't
able to easily figure out how to do that with a `ops = { path =
"ci/path/for/ops/branch" }` type specifier. It seems like this approach
is at least an improvement on the existing one, even if not perfect. (It
also will unblock other PRs, given that the tests fail because we're
re-locking in entirety).

Fixes #1272.
  • Loading branch information
tonyandrewmeyer committed Jun 26, 2024
1 parent 79706f4 commit 6a2b165
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion .github/workflows/db-charm-tests.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ jobs:
echo -e "\ngit+$GITHUB_SERVER_URL/$GITHUB_REPOSITORY@$GITHUB_SHA#egg=ops" >> requirements.txt
else
sed -i -e "s/^ops[ ><=].*/ops = {path = \"myops\"}/" pyproject.toml
poetry lock
poetry lock --no-update
fi
- name: Install dependencies
Expand Down

0 comments on commit 6a2b165

Please sign in to comment.