{"id":53914,"date":"2020-11-27T12:11:00","date_gmt":"2021-02-09T14:41:28","guid":{"rendered":"https:\/\/www.globallogic.com\/ua\/insights\/blogs\/ci-cd-%d0%b4%d0%bb%d1%8f-js-%d1%80%d0%be%d0%b7%d1%80%d0%be%d0%b1%d0%bd%d0%b8%d0%ba%d1%96%d0%b2-%d1%87%d0%b0%d1%81%d1%82%d0%b8%d0%bd%d0%b0-%d0%bf%d0%b5%d1%80%d1%88%d0%b0-%d1%82%d0%b5%d0%be%d1%80\/"},"modified":"2025-01-31T04:46:33","modified_gmt":"2025-01-31T04:46:33","slug":"ci-cd-for-js-devs-theory","status":"publish","type":"insightsection","link":"https:\/\/www.globallogic.com\/ua\/insights\/blogs\/ci-cd-for-js-devs-theory\/","title":{"rendered":"CI\/CD \u0434\u043b\u044f JS \u0440\u043e\u0437\u0440\u043e\u0431\u043d\u0438\u043a\u0456\u0432. \u0427\u0430\u0441\u0442\u0438\u043d\u0430 \u043f\u0435\u0440\u0448\u0430 – \u0442\u0435\u043e\u0440\u0456\u044f"},"content":{"rendered":"
\n
Author: Inna Ivashchuk, Senior Software Engineer, Engineering, Consultant, GlobalLogic Ukraine<\/span><\/span><\/em><\/h6>\n

In this column, I want to talk about automation (where would we go without it). Let’s try to improve the development process and the life of a JS developer and find out what are the advantages of CI\/CD practices, what is the difference between CI vs CD vs CD. And next week we’ll get down to the practical part and try to get <\/span><\/span>Travis CI up and running. So, let’s go!\u00a0<\/span><\/span><\/span><\/p>\n

CI: What is it and why?<\/span><\/span><\/span><\/h3>\n

I think you have repeatedly come across the term <\/span><\/span>Continuous integration (or CI for short)<\/span><\/span><\/strong> , but what exactly is meant by the use of CI?<\/span><\/span><\/p>\n

Today we will try to figure it out. Before continuing with CI\/CD practices, it is worth mentioning version control systems such as git, svn, mercurial and others. Most likely, most of you are part of a team, and in order to work comfortably, control the code of the application, which changes every day, we need a VCS tool that will help to synchronize the changes of several developers without problems.<\/span><\/span><\/p>\n

\n

\"\"<\/p>\n<\/div>\n

To understand in more detail the interdependence between the version control system and the practice <\/span><\/span>of Continuous integration<\/span><\/span><\/strong> , let’s look at the diagram above: we have a developer, a version control system, and of course AI. From this diagram, it follows that Continuous integration is a practice that allows you to run automatic checks, such as tests, during each change (new commit), creation of a pull\/merge request. If the tests were successful, the project build is started and, as a result, we get an artifact. In our case, the artifact can be, for example, a docker image, which we will use later, or it can be static files that we will immediately publish on Heroku, or on GitHub pages, or on surge, or on our own hosting (VPS ). This, in principle, is not important, because the configuration can be adjusted according to needs.<\/span><\/span><\/p>\n

Now let’s deal with the stages of CI:<\/span><\/span><\/strong><\/p>\n