You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a project for which the build is really complicated and long. Also the resulting aar is around 20Mb.
So committing the release aar is not a good choice, and jitpack.io wont build the repo.
Is (could) there a way to tell jipack.io to "serve" a aar from a github release?
If not i think it would be a great addition. It would also reduce global storage usage as releases are already stored on github.
The text was updated successfully, but these errors were encountered:
I have a similar case where I must publish the already pre-built ARR.
To do this, I created a separate repository where I keep the already pre-built AAR, and publish config looks like this:
I have a project for which the build is really complicated and long. Also the resulting aar is around 20Mb.
So committing the release aar is not a good choice, and jitpack.io wont build the repo.
Is (could) there a way to tell jipack.io to "serve" a aar from a github release?
If not i think it would be a great addition. It would also reduce global storage usage as releases are already stored on github.
The text was updated successfully, but these errors were encountered: