[Epic] Improve test matrix to include all supported spring versions
@rujche is already working on this.
Since May 15, 2026.
Assessment
This issue has not been assessed yet.
Description
Context:
Currently Spring Cloud Azure supports multi Spring Boot and Spring Cloud versions, but those versions are not actively tested.
we need to figure out how to enable a testing matrix to actively test all support spring versions and Spring Cloud Azure libraries.
- Spring projects release monthly.
- Several types of libraries can be released from Spring projects, snapshot, prerelease, and GA.
- We use multiple Spring projects in Spring Cloud Azure: Spring Framework, Spring Boot, Spring Data, Spring Integration, Spring Cloud Stream, etc.
Strong has a poc for how to get dependency versions: https://github.com/Azure/spring-cloud-azure-tools/tree/t1/src/main/java/com/azure/spring/dev/tools/dependency
Goal:
The Spring Cloud Azure dev branch should align with Spring Boot on the current Spring Boot version.
- Spring Cloud Azure's source code dependency version should rely on the return value from
https://spring.io/project_metadata/spring-bootwithcurrent: true. - When the current version from
https://spring.io/project_metadata/spring-bootchanges, we should catch up ASAP. - Track:
- #5
- Need to change the PR contents https://github.com/Azure/spring-cloud-azure-tools/pull/10
The Spring Cloud Azure dev branch should maintain a test matrix for dependent Spring projects. -- UT
- Spring Cloud Azure defines their supported Spring Boot versions,
- The supported versions change along with Spring releases.
- Such as
supported-versions.json, listing 2.5.1 and 2.6.1 for example.
- Spring Cloud Azure tests on each milestone and GA releases of dependent Spring projects.
- Track:
- https://github.com/Azure/spring-cloud-azure-tools/issues/7
- Need to set different startup methods to start different test scopes https://github.com/Azure/azure-sdk-for-java/issues/29794
The Spring Cloud Azure should have integration tests, containing all Spring Cloud Azure libraries, to run against each version. -- IT
- Ideally, we can call Azure Spring Initializr to generate such a sample project and run it, expecting it throws no exceptions.
- If not the ideal case, we can write such a sample project (probably we put it in the SDK repo) and run it against each version. https://github.com/Azure/azure-sdk-for-java/issues/29717
- Optional IT tasks will work on:
Solutions
- The Spring Cloud versions, should be parsed from API like
curl -G https://start.spring.io/pom.xml -d packaging=war -o pom.xmland retrieved automatically - The version matrix should be persistent somewhere, such as spring-cloud-azure-tools repo.
Originally posted by @saragluna in https://github.com/microsoft/spring-cloud-azure/discussions/930#discussioncomment-2704557
- Dominant language
- Java
- Stars
- 4
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
PhasetransCrystal/FPSMatch#47 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 76/100
apache/maven-toolchains-plugin#205 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
[Bug] Dated CSV export filenames use the UTC day rather than the operator dayPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
apache/rocketmq-dashboard#6896 ·
Maintainers usually reply within 3 days