Switch Spring integration workflow from Maven to Bazel#4770
Conversation
|
@copilot modify the cache key so it is the same as other CI/CD so that it re-uses builds from the main build/test runs. |
Updated in |
|
@copilot since bazel is building jars, can we cache them across OS versions? |
Implemented in |
|
@copilot update the main CI to cache across OS also. |
Implemented in |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: brendandburns, Copilot The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Spring integration CI was still using Maven, diverging from the repository’s Bazel-based build/test path. This updates the
springGitHub Actions workflow to run Spring + Spring AOT integration builds/tests via Bazel targets.Workflow execution model
@maven//:pin) to keep external resolution aligned withMODULE.bazel.Runner/tooling setup
BAZELISK_SKIP_VERSION_CHECK=1in job env for consistent CI execution.Caching strategy
MODULE.bazel,.bazelversion,maven_install.json) and Java matrix version.