poc: attempt to create a simple, standard set of jobs & commands#377
poc: attempt to create a simple, standard set of jobs & commands#377effervescentia wants to merge 8 commits intomasterfrom
Conversation
|
Your development orb has been published. It will expire in 30 days. |
|
Your development orb has been published. It will expire in 30 days. |
|
Your development orb has been published. It will expire in 30 days. |
|
Your development orb has been published. It will expire in 30 days. |
There was a problem hiding this comment.
std_checkout and std_clone can be a single job since they are basically the same (default to $CIRCLE_SHA1 and $CIRCLE_PROJECT_REPONAME)
do we have anywhere that we need multiple branches or commits upfront? CircleCI checkout defaults to a blobless checkout. But I think we may only need 2 kinds:
- single branch shallow clone: the latest object state of single commit without history (building, linting, sonarcloud, hadolint)
- treeless clone of master with tags: semantic-release uses commits and tags for determining next version. however, semantic-release may be doing git commands internally, i'd have to look again
| working_directory: /home/circleci/code | ||
| command: | | ||
| yarn install --immutable | ||
| - std_save_cache: |
There was a problem hiding this comment.
i have found that CircleCI save_cache/restore_cache is good for caching between workflows, and that persist_to_workspace/attach_workspace is good for caching between jobs of the same workspace.
So we would still want to persist .yarn/cache and ./node_modules to the workspace and then any job that needs them (build, test_*, etc) would require this job and attach_workspace.
This is especially true for anything that requires the build job. Since restore_cache could pull a stale cache from a different workflow we didn't really want, but attach_workspace guarantees that whatever is attach was put there from this workflow.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
|
Your development orb has been published. It will expire in 30 days. |
3 participants
No description provided.