Group items tagged

Filter: All | Bookmarks | Topics Simple Middle

shared by crazylion lee on 16 Apr 17 - No Cached

shared by crazylion lee on 16 Apr 17 - No Cached

shared by 張旭 on 25 Nov 18 - No Cached

Repeatability is also important
...

Cancel
When a CI process isn’t repeatable you’ll find yourself wasting time re-running jobs to get them to go green.
...

Cancel
Workspaces persist data between jobs in a single Workflow.
...

Cancel
...9 more annotations...
Caching persists data between the same job in different Workflow builds.
...

Cancel
Artifacts persist data after a Workflow has finished
...

Cancel
When a Workspace is declared in a job, one or more files or directories can be added. Each addition creates a new layer in the Workspace filesystem. Downstreams jobs can then use this Workspace for its own needs or add more layers on top.
...

Cancel
Unlike caching, Workspaces are not shared between runs as they no longer exists once a Workflow is complete.
...

Cancel
Caching lets you reuse the data from expensive fetch operations from previous jobs.
...

Cancel
A prime example is package dependency managers such as Yarn, Bundler, or Pip.
...

Cancel
Caches are global within a project, a cache saved on one branch will be used by others so they should only be used for data that is OK to share across Branches
...

Cancel
Artifacts are used for longer-term storage of the outputs of your build process.
...

Cancel
If your project needs to be packaged in some form or fashion, say an Android app where the .apk file is uploaded to Google Play, that’s a great example of an artifact.
...

Cancel