SoftwareApp 2690e53662 The release gate names the baseline-profile task it means ...

verify.sh --release asked for :baselineprofile:assembleBenchmark, which the baseline-profile plugin made ambiguous when it added a benchmark flavour on top of the benchmark build type - so the task failed before the release build, and the nightly release job has been red without anyone seeing it. The ambiguous name is replaced with assembleBenchmarkBenchmark, with a comment saying why it is spelled out. verify.sh --release is green again.

2026-10-18 11:21:15 +02:00

..

store-assets

M10: store assets - Plain Files naming, generated icon/feature graphic, listing copy

2026-10-14 17:47:02 +02:00

benchmark-fixture.sh

Make the benchmark fixture reusable, since building it is the expensive part

2026-10-17 21:04:25 +02:00

benchmark-report.py

The benchmark runs in CI, and fails when the jank metric is missing

2026-10-17 23:00:22 +02:00

benchmark-watch-install.sh

Record the first complete benchmark run, and what its numbers are not

2026-10-17 15:26:59 +02:00

make-code-map.py

Add a macrobenchmark module, and find out what the build was hiding

2026-10-17 09:45:36 +02:00

make-demo-library.py

Screenshots: demo-library generator, per-form-factor targets, listing notes

2026-10-14 17:52:40 +02:00

make-store-assets.sh

M10: store assets - Plain Files naming, generated icon/feature graphic, listing copy

2026-10-14 17:47:02 +02:00

make-store-screenshots.sh

Screenshots: 10-inch tablet set; guard against blank captures

2026-10-14 23:44:24 +02:00

measure-startup.sh

Test the interface as a user sees it, and let a debug build tell on itself

2026-10-17 09:23:11 +02:00

verify.sh

The release gate names the baseline-profile task it means

2026-10-18 11:21:15 +02:00