![]() It is also the target environment for all application code changes made by application developers.Īlso, there are so-called production-like environments. Generally, end users interact with an application in the production environment. To fully appreciate this article, readers are advised to get a good understanding of these terms. We suppose our readers are familiar with the following git-related terms: branch, tag, master, commit, merge, rebase, fast-forward merge, and the git push-force procedure. However, werf supports only the Git version control system. NOTICE: In the text below, the term “git” can be interpreted as a common name for any version control system. We also recommend you to read one the following guides about configuring the specific CI/CD system: We will start with defining some basic terms like environment and workflow, and then move on to workflow building blocks and describe some ready-to-use workflows that can be constructed using provided workflow building blocks. ![]() CI/CD consists of 2 parts: CI means continuous integration of application code changes into the main codebase, and CD means continuous delivery of these changes to the end user. In this article, we will discuss what CI/CD means and overview CI/CD workflows that can be implemented with werf.Īs you know, the primary purpose of using CI/CD for any project is to deliver application code changes to the end user as fast as possible.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |