chore: enable rosetta cache for builds#17336
Conversation
Avail ourselves of the new build cache feature in cdklabs/cdk-ops#1776. Adds two new things: **A persistently cached directory** The directory `$HOME/.s3buildcache` will be stored and restored in the S3 bucket, if configured. The build can assume that files it puts in there will be availble on the next build (and on the corresponding PR build). **Cache rosetta tablet** If there is a file in the persistent cache directory for Rosetta, pass it to `jsii-rosetta` as an input. Afterwards, store whatever tablet the build produced back into the cache directory. The latter will only impact the persistent cache if done on a build that is actually configured to store the cache back, which is only the main pipeline build.
| cachedir=$HOME/.s3buildcache | ||
| mkdir -p $cachedir |
There was a problem hiding this comment.
~ (Nit) - Move this to after the env variable check so this script no-ops if the environment variable isn't set.
There was a problem hiding this comment.
Actually I did this on purpose. It's convenient to always be able to rely on the ~/.s3buildcache directory existing (whether it's empty or not).
Makes the shell scripts easier to write... (?)
|
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
|
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Avail ourselves of the new build cache feature in cdklabs/cdk-ops#1776. Adds two new things: **A persistently cached directory** The directory `$HOME/.s3buildcache` will be stored and restored in the S3 bucket, if configured. The build can assume that files it puts in there will be availble on the next build (and on the corresponding PR build). **Cache rosetta tablet** If there is a file in the persistent cache directory for Rosetta, pass it to `jsii-rosetta` as an input. Afterwards, store whatever tablet the build produced back into the cache directory. The latter will only impact the persistent cache if done on a build that is actually configured to store the cache back, which is only the main pipeline build. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Avail ourselves of the new build cache feature in cdklabs/cdk-ops#1776. Adds two new things: **A persistently cached directory** The directory `$HOME/.s3buildcache` will be stored and restored in the S3 bucket, if configured. The build can assume that files it puts in there will be availble on the next build (and on the corresponding PR build). **Cache rosetta tablet** If there is a file in the persistent cache directory for Rosetta, pass it to `jsii-rosetta` as an input. Afterwards, store whatever tablet the build produced back into the cache directory. The latter will only impact the persistent cache if done on a build that is actually configured to store the cache back, which is only the main pipeline build. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Avail ourselves of the new build cache feature in cdklabs/cdk-ops#1776.
Adds two new things:
A persistently cached directory
The directory
$HOME/.s3buildcachewill be stored and restored in theS3 bucket, if configured. The build can assume that files it puts in
there will be availble on the next build (and on the corresponding
PR build).
Cache rosetta tablet
If there is a file in the persistent cache directory for Rosetta,
pass it to
jsii-rosettaas an input.Afterwards, store whatever tablet the build produced back into the
cache directory.
The latter will only impact the persistent cache if done on a build
that is actually configured to store the cache back, which is only
the main pipeline build.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license