Skip to content

Restore default build targets and add fastBuild#3081

Merged
CydeWeys merged 1 commit into
google:masterfrom
CydeWeys:fix-build
Jun 4, 2026
Merged

Restore default build targets and add fastBuild#3081
CydeWeys merged 1 commit into
google:masterfrom
CydeWeys:fix-build

Conversation

@CydeWeys
Copy link
Copy Markdown
Member

@CydeWeys CydeWeys commented Jun 3, 2026

This commit reverts changes from 5599a0e and most of 5286b1a (PR #3068) that stripped essential dependencies (buildConsoleForAll, buildNomulusImage, buildToolImage, fragileTest) from the default './gradlew build' target, which broke downstream deployment pipelines. It restores the default build to generate all artifacts and images.

It also removes the now-redundant 'buildAll' alias, and replaces it with a new 'fastBuild' target designed explicitly for local developers and CI checks that need to skip heavy Docker/Angular compilations and fragile tests.

Sequential execution constraints for parallel Angular builds are preserved.


This change is Reviewable

@CydeWeys CydeWeys requested a review from ptkach June 3, 2026 16:43
@CydeWeys CydeWeys force-pushed the fix-build branch 2 times, most recently from 1116eea to 9e60f2a Compare June 3, 2026 20:04
This commit reverts changes from 5599a0e and most of 5286b1a (PR google#3068) that stripped essential dependencies (buildConsoleForAll, buildNomulusImage, buildToolImage, fragileTest) from the default './gradlew build' target, which broke downstream deployment pipelines. It restores the default build to correctly generate all necessary production artifacts and Docker images.

It introduces a new 'fastBuild' target designed explicitly for local developers and CI checks. This lightweight target disables the execution of heavy Docker image builds, Angular compilations, and fragile tests to provide rapid feedback. Sequential execution constraints for parallel Angular builds are maintained to prevent cache corruption.

It updates the ':core:generateSqlSchema' task to execute using the 'unittest' environment instead of 'alpha'. The 'alpha' configuration is a private, internal environment config that is not distributed in the open-source repository, which caused the task to fail for public contributors. By switching to 'unittest', the generator can successfully run using the public test configuration. With this fixed, it also includes the newly generated 'db-schema.sql.generated' file, which now correctly tracks the 'FORBID_INSECURE_ALGORITHMS_RFC_9904' feature flag that was recently added.

Finally, it implements a split-runner execution strategy for the 'sqlIntegrationTest' task to permanently resolve 'failed to discover tests' and 'NoSuchMethodError' exceptions on Kokoro. Because Kokoro tests cross-version compatibility against both legacy deployed artifacts (compiled with JUnit 4 @RunWith wrappers) and modern artifacts (compiled with JUnit 5 @suite annotations), we cannot statically configure a single test runner. We now dynamically run both the legacy 'useJUnit()' and modern 'useJUnitPlatform()' runners sequentially with 'failOnNoDiscoveredTests' disabled, allowing the appropriate engine to discover and execute the suite without causing classpath collisions.
@CydeWeys CydeWeys added this pull request to the merge queue Jun 4, 2026
Merged via the queue into google:master with commit 75524fd Jun 4, 2026
14 of 15 checks passed
@CydeWeys CydeWeys deleted the fix-build branch June 4, 2026 16:37
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.

2 participants