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

Reuse previous build artifacts if they are available and their inputs are unchanged #6882

Open
str4d opened this issue May 6, 2024 · 0 comments
Labels
A-build Area: Build system A-CI Area: Continuous Integration I-performance Problems and improvements with respect to performance

Comments

@str4d
Copy link
Contributor

str4d commented May 6, 2024

Currently in the GitHub Actions CI workflow, whenever a PR changes we build for all target platforms. We speed up builds by caching both the built dependencies, and CCache files for the main build. However, it is common to be editing a file that does not affect the build process but does affect CI (for example, the CI workflow itself, or the RPC test files). In these situations, it would be both faster and more resource efficient to reuse the build artifacts from a previous CI run.

I don't know if there's any reasonable way to do this inside the GH Artifacts pathway, or whether we'd need to move these files to the GH Cache pathway.

This isn't attempting to integrate reproducible builds into CI; we don't care in this case whether the binary is bit-for-bit identical, but just that the changes the PR is making are not to inputs to the build.

@str4d str4d added I-performance Problems and improvements with respect to performance A-build Area: Build system A-CI Area: Continuous Integration labels May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-build Area: Build system A-CI Area: Continuous Integration I-performance Problems and improvements with respect to performance
Projects
None yet
Development

No branches or pull requests

1 participant