29장. Cache vs Artifacts

 

https://docs.gitlab.com/ee/ci/caching/#cache-vs-artifacts

Caching in GitLab CI/CD | GitLab

 

 

## Artifacts - 산출물 저장

## Cache - 프로젝트 의존성 일시 저장

 

I wanted to take a minute to quickly go over the difference between cash and artifacts.

Now, cash and artifacts they made seem very similar to one another.

They have a very similar configuration and they sort of will behave in a similar way, but they are

not the same thing and they serve different purposes.

We have used artifacts of art to save output from the Bell job.

Now, this is not the only purpose of the artifact.

The artifact can be something that is passed between jobs and wear.

Different stages of the job can add other things to it.

So, for example, the build process itself can span over multiple jobs and multiple stages, so it

doesn't mean that the job has to do everything in one stage, in one job, so it can imagine having

different stages with different jobs.

And it's each stage that's something to the build.

And you can use artifacts in this case to pass this information from one stage to the next stage, from

one job to the next job.

And you do not have to use cash for that.

And it is not useful for keeping any builders on.

So anything that you have built, regardless of kind of application you have, you do not want to use

the cash to replace the artifact because this is not really the purpose of the cash now in old exemplars

that we have used so far.

You could theoretically have used the cash to do that.

So don't use it because this is not really the purpose of the cash.

So I hope I have made the difference between cash and artifacts clear and definitely make sure you check

the resources to this lecture, because I will be posting some additional information regarding this.