Skip to content
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

Build PRs using artifact registry packages #1862

Merged
merged 3 commits into from
Oct 29, 2024

Conversation

Polber
Copy link
Contributor

@Polber Polber commented Sep 11, 2024

This PR configures maven on GitHub Actions workers (self-hosted) to pull dependencies from a Google-hosted artifact registry. This ensures that PR's are able to stage templates the same way that templates are staged during the release process to detect possible package discrepancies earlier.

Copy link

codecov bot commented Sep 20, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 45.08%. Comparing base (b72eaa2) to head (04bc025).
Report is 4 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main    #1862      +/-   ##
============================================
- Coverage     45.09%   45.08%   -0.01%     
+ Complexity     3935     3609     -326     
============================================
  Files           835      835              
  Lines         49703    49703              
  Branches       5232     5232              
============================================
- Hits          22412    22411       -1     
  Misses        25625    25625              
- Partials       1666     1667       +1     
Components Coverage Δ
spanner-templates 66.26% <ø> (-0.01%) ⬇️
spanner-import-export 64.18% <ø> (-0.03%) ⬇️
spanner-live-forward-migration 76.18% <ø> (ø)
spanner-live-reverse-replication 76.54% <ø> (ø)
spanner-bulk-migration 85.57% <ø> (ø)

see 1 file with indirect coverage changes

@Polber Polber changed the title Build release using artifact registry packages Build PRs using artifact registry packages Sep 25, 2024
@Polber Polber force-pushed the jkinard/release-ar branch 6 times, most recently from e61345b to c379cf8 Compare October 8, 2024 18:52
@Polber Polber marked this pull request as ready for review October 10, 2024 13:42
@Polber Polber requested a review from damccorm October 10, 2024 13:42
@damccorm
Copy link
Contributor

Could you add a description of what/why this is doing now that we pulled out the urgent pieces? It does also look like checks might be persistently failing (not sure if that's a flake or not)

@Polber
Copy link
Contributor Author

Polber commented Oct 11, 2024

@damccorm It's also hard to test because new caches get created by other workflows which affect this one being able to use AR packages instead of maven central. Once it is merged, I'll be able to clear caches and all new ones will use AR packages.

I'm pretty confident this change works, but let's wait until next week to merge so I can keep an eye on actions and see if anything fails.

@Polber Polber requested a review from damccorm October 15, 2024 15:36
Copy link
Contributor

@damccorm damccorm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - feel free to merge at a time when you're able to monitor/rollback if needed

cicd/cmd/run-build/main.go Show resolved Hide resolved
Signed-off-by: Jeffrey Kinard <[email protected]>
Signed-off-by: Jeffrey Kinard <[email protected]>
@Polber Polber self-assigned this Oct 29, 2024
@Polber Polber merged commit 7532a11 into GoogleCloudPlatform:main Oct 29, 2024
7 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants