Skip to content

ci: wave 9 evidence for path-filtered workflows (throwaway) - #57

Closed
DoDiODev wants to merge 2 commits into
release-wave9-basefrom
ci/wave9
Closed

DoDiODev wants to merge 2 commits into
release-wave9-basefrom
ci/wave9

Conversation

@DoDiODev

Copy link
Copy Markdown
Owner

Throwaway: wave 9 + a comment line in a .sh file so that unit-test and test-e2e run. Will be closed.

`backend/Dockerfile` still installed mockery v3.7.2 while the Makefile,
`Dockerfile.local` and `scripts/install-mockery.sh` (used by CI) are on
v3.7.4, so the generated mocks depended on which build path was used.

- Bump the `backend/Dockerfile` pin to v3.7.4.
- Introduce `MOCKERY_VERSION` (default v3.7.4) and
  `MOCKERY ?= GOOS= GOARCH= CGO_ENABLED=0 go run
  github.com/vektra/mockery/v3@$(MOCKERY_VERSION)` in the Makefile;
  `make mock` and `make go-dep` use them. `make mock` thus no longer
  depends on whatever `mockery` is on the PATH (the CI builder image
  `mericodev/lake-builder:latest` ships mockery v2, which cannot read the
  v3 YAML configuration). GOOS/GOARCH are cleared so the tool is built for
  the host even when `backend/Dockerfile` cross-compiles `make all`.
  `MOCKERY=mockery make mock` keeps the old behaviour.
@DoDiODev

Copy link
Copy Markdown
Owner Author

Evidence done: 8/8 upstream workflows green on 6c9a7b9 (wave 9 + trigger).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant