Always download Gradle from MASS in CI#11493
Always download Gradle from MASS in CI#11493gh-worker-dd-mergequeue-cf854d[bot] merged 2 commits into
Conversation
🟢 Java Benchmark SLOs — All performance SLOs passed
Commit: Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion. |
This comment has been minimized.
This comment has been minimized.
fd82c55 to
6298111
Compare
Gradle smoke tests should not reach services.gradle.org from CI. They now take the MASS read URL as an optional distribution base and keep the regular Gradle version path for local runs. The smoke-test plugin, daemon helpers, launcher wrapper rewrite, and TestKit fixture share the same URL decision. CI Visibility snapshots are refreshed for the deterministic fixture shape.
6d7fa24 to
d6c1177
Compare
There was a problem hiding this comment.
Great! Was planning on tackling this myself on SDTEST-3815 so thanks for taking care of it 🚀
AlexeyKuznetsov-DD
left a comment
There was a problem hiding this comment.
LGTM.
Left minor comment.
Would be nice to see in PR description how tests passed on CI.
Build MASS distribution URLs by first ensuring the base URL ends with a slash, then appending the artifact path without a leading slash. The Java and Kotlin helpers now read the same way and the unit test covers both input shapes.
|
/merge |
|
View all feedbacks in Devflow UI.
This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
The expected merge time in
|
858b33c
into
master
What Does This Do
Follow-up to #11461, This applies MASS in parts that drive gradle in different versions
Motivation
Additional Notes
Contributor Checklist
type:and (comp:orinst:) labels in addition to any other useful labelsclose,fix, or any linking keywords when referencing an issueUse
solvesinstead, and assign the PR milestone to the issue/merge. You can also:/merge --commit-message "..."/merge -c/merge -f --reason "reason"; please use this judiciously, as some checks do not run at the PR-levelJira ticket: [PROJ-IDENT]