<p>One argument in support of storing artifacts is that it promotes consistency when deploying across different environments.</p>
<p>From <a href="https://continuousdelivery.com" rel="nofollow noreferrer"><em>Continuous Delivery</em></a> by Humble and Farley:</p>
<blockquote>
<p>Every time you compile the code, you run the risk of introducing some difference. The version of the compiler installed in the later stages may be different from the version that you used for your commit tests. You may pick up a different version of some third-party library that you didn’t intend. Even the configuration of the compiler may change the behavior of the application.</p>
</blockquote>
<p>By only building artifacts once, we make sure that the production code is exactly the same as that which has gone through testing. In very small codebases with simple pipelines, it might not make too much of an impact, but it's still best practice to only build once.</p>

CC BY-SA 4.0
2020-08-01T23:09:30.053Z
Those are compelling reasons.|
 
As a devops engineer i can't ensure that all builds will use the same dependencies every time.

Also, despite the fact that my builds run in a docker container, it gives me the freedom  to update containers at any time without risk of inconsistency.

Thanks.
gabrielpe
CC BY-SA 4.0
2020-07-31T16:00:36.583Z
2020-07-31T16:00:36.583Z
Meow_ly
<p>Why should I store artifacts? I'm doing it but i don't know if it still make sense.</p>
<ul>
<li>My builds are fairly quick</li>
<li>I do git tag versioning</li>
<li>None of my builds depends on another. (all independent micro-services)</li>
</ul>
<p>Any compelling reason to keep this &quot;Artifactory code&quot; in my pipelines?</p>

<artifacts>
Why should I store artifacts?
gabrielpe
# Why should I store artifacts?

(Asked by: username_0 on 2020-07-31)

Why should I store artifacts? I'm doing it but i don't know if it still make sense.

* My builds are fairly quick
* I do git tag versioning
* None of my builds depends on another. (all independent micro-services)

Any compelling reason to keep this "Artifactory code" in my pipelines?

**Tags:** artifacts


---

## 1 answers

### Answer by username_1 on 2020-07-31. Score: 3 | Accepted answer

One argument in support of storing artifacts is that it promotes consistency when deploying across different environments.

From [*Continuous Delivery*](https://continuousdelivery.com) by Humble and Farley:

> Every time you compile the code, you run the risk of introducing some difference. The version of the compiler installed in the later stages may be different from the version that you used for your commit tests. You may pick up a different version of some third-party library that you didn’t intend. Even the configuration of the compiler may change the behavior of the application.

By only building artifacts once, we make sure that the production code is exactly the same as that which has gone through testing. In very small codebases with simple pipelines, it might not make too much of an impact, but it's still best practice to only build once.

> **Comments:**
> **username_0**: Those are compelling reasons.|   As a devops engineer i can't ensure that all builds will use the same dependencies every time.  Also, despite the fact that my builds run in a docker container, it gives me the freedom  to update containers at any time without risk of inconsistency.  Thanks.  

---

