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

Cache extension build results #232

Open
Tracked by #8931
britzl opened this issue Jun 8, 2022 · 4 comments
Open
Tracked by #8931

Cache extension build results #232

britzl opened this issue Jun 8, 2022 · 4 comments

Comments

@britzl
Copy link
Contributor

britzl commented Jun 8, 2022

To speed up CI builds (which are usually run from a clean environment) where extensions rarely change it will help if extension outputs (library+resources) are cached on the extender server.

@britzl
Copy link
Contributor Author

britzl commented Dec 19, 2022

Add metrics first to measure before and after this change.

This will reduce build time. The downside is that it will increase storage requirements (and by extension costs).

@JCash
Copy link
Contributor

JCash commented May 13, 2023

Metrics ticket: #289

@JCash
Copy link
Contributor

JCash commented May 13, 2023

Perhaps do it in these steps:

  1. full upload
  2. extensions
  3. libraries
  4. jars

@AGulev
Copy link
Contributor

AGulev commented Oct 18, 2023

Also, it makes sense to take into account situations when the only change is changes in manifests.
For example, CI builds game and increase version number in game.project. This version number ends up in AndroidManifest.xml. And this is the only change from the previous build.

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

No branches or pull requests

3 participants