I will not focus on the image creation at this time. For our case, the Container Image produced at the end of the build will be our Build Artifact.Īnd the good part is that Build Artifact are immutable!Īs in the last article, we want to create our container image with all we need for our application to function properly. Build artifacts can be nearly anything that your team needs to test or deploy your app. While in the first article of the series we explored the "Base Registry" approach to promote a Container image across different environments, in this second part we will get rid of the additional registry and we will use a Build Artifact instead.īuild artifacts are the files that you want your build to produce. In this series, I will explore different ways to do so. When you use containers for your application, one of the things you need to think about is how to move (aka promote) the container images you generate across different environments.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |