-
Notifications
You must be signed in to change notification settings - Fork 44
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
Add demo app to CI builds #365
Add demo app to CI builds #365
Conversation
Resolves #364 |
-dontwarn com.fasterxml.jackson.core.JsonGenerator | ||
-dontwarn com.google.auto.value.AutoValue$Builder | ||
-dontwarn com.google.auto.value.AutoValue | ||
-dontwarn com.google.auto.value.extension.memoized.Memoized |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minification was failing without this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cheers!
* add demo app to ci builds * run from subdir * add jar * fixing build * need to touch the demo local.properties too * demo app gets its on version catalog * try and get renovate to chill out in the demo app project * add name * scale image down * more dep updates * remove root local.properties * add target sdk for app * simplify catalog
A little late to this but yeah this seems like the right move. The demo app can also pull in new versions of Android libraries that the agent doesn't need, so I think we'll get here eventually anyway |
Part of the reason for having the demo-app is to show features, but those features are meaningless if the usage of those doesn't work. We need to build the demo app with every PR and merge to main, in order to ensure compatibility.
I guess I should also mention that this provides the
demo-app
with its own version catalog. I think this is going to be required in order for us to version it separately (via renovate) without impacting the main build. It's some additional duplication, unfortunately, but I think it's needed given the multi-project approach we've chosen.