-
Notifications
You must be signed in to change notification settings - Fork 597
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor bom generation #6675
Refactor bom generation #6675
Conversation
📝 PRs merging into main branchOur main branch should always be in a releasable state. If you are working on a larger change, or if you don't want this change to see the light of the day just yet, consider using a feature branch first, and only merge into the main branch when the code complete and ready to be released. |
1 similar comment
📝 PRs merging into main branchOur main branch should always be in a releasable state. If you are working on a larger change, or if you don't want this change to see the light of the day just yet, consider using a feature branch first, and only merge into the main branch when the code complete and ready to be released. |
Vertex AI Mock Responses Check
|
plugins test results66 tests 66 ✅ 1m 15s ⏱️ Results for commit b45fc48. |
Size Report 1Affected ProductsNo changes between base commit (92f448f) and merge commit (fd10f74).Test Logs |
Coverage Report 1Affected Products
Test Logs |
Per b/394616465,
This refactors our bom generation and all of the bom related tasks to solve the following issues:
Effectively, this PR splits bom generation into 3 tasks:
GenerateBomTask
,GenerateBomReleaseNotesTask
, andGenerateTutorialBundleTask
. These 3 tasks get ran together during the release, but them being separated now makes it easier to not only run them in isolation of each other- but test them in isolation. As such, this PR also includes tests for all of the bom related tasks, and documentation for everything. These tasks also take advantage of the newGMavenService
- to support proper parallel execution and caching. And finally, the configuration of these tasks has been moved to the use-site instead of the declaration site, to more cleanly match other tasks and the configuration style that the Gradle team pushes.This PR also fixes the following: