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-tools] skip throwing MAVEN_CACHE_ERROR if Could not find BlurView-version-2.0.3.jar line is present #505

Conversation

szdziedzic
Copy link
Member

@szdziedzic szdziedzic commented Jan 27, 2025

Why

These alerts are getting way too noisy. All of these are false positives. This BlurView package in this version was just deleted from jitpack.

How

Don't throw MAVEN_CACHE_ERROR if the Could not find BlurView-version-2.0.3.jar line is present in logs

Test Plan

Tests

Copy link
Member Author

@szdziedzic szdziedzic marked this pull request as ready for review January 27, 2025 11:59
Copy link
Contributor

@radoslawkrzemien radoslawkrzemien left a comment

Choose a reason for hiding this comment

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

Good call 🚀

@@ -299,7 +299,11 @@ export const buildErrorHandlers: ErrorHandler<TrackedBuildError>[] = [
phase: BuildPhase.RUN_GRADLEW,
regexp: ({ env }: ErrorContext) =>
env.EAS_BUILD_MAVEN_CACHE_URL
? new RegExp(escapeRegExp(env.EAS_BUILD_MAVEN_CACHE_URL))
? new RegExp(
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe it would be worth it to add a comment with context for this regex

@szdziedzic szdziedzic merged commit 7591992 into main Jan 27, 2025
5 checks passed
@szdziedzic szdziedzic deleted the 01-27-_build-tools_skip_throwing_maven_cache_error_if_could_not_find_blurview-version-2.0.3.jar_line_is_present branch January 27, 2025 12:04
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