Cache ci build artifacts
See original GitHub issueCurrently, each CI job runs yarn build
on monorepo to generate non-stubbed dist
artifacts but it takes ~1.:30
which is only needed once! We might cache it in a prepared job and restore packages/*/dist
on the next steps.
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
GitLab CI: Cache and Artifacts explained by example
Artifacts are files stored on the GitLab server after a job is executed. Subsequent jobs will download the artifact before script execution.
Read more >Caching in GitLab CI/CD
Use artifacts to pass intermediate build results between stages. Artifacts are generated by a job, stored in GitLab, and can be downloaded. Both...
Read more >What is the correct usage of cache/artifacts in Gitlab CI?
Artifacts should be used to permanently make available any files you may need at the end of a pipeline, for example generated binaries, ......
Read more >Difference between caches and artifacts in GitLab CI - Dev Tips
Artifacts can't be used in a different pipeline. Use artifacts to pass intermediate build results between stages of the same pipeline. Caches ......
Read more >Artifacts, Caching, and Local Storage for HPC Projects
GitLab offers a caching mechanism as part of the CI pipeline. When caching is defined for a CI job all identified files/directories will...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@pi0 Let me know when the pending issue is resolved.
Sure, I can have a look