<\/p>\n
Juan Ezquerro, System Administrator at PaynoPain<\/strong><\/p>\n <\/p>\n Continuous integration<\/strong> is a development practice whose name, as it is easily deduced, is descriptive and literal. To apply it, we rely on continuously verifying the code to be able to integrate improvements little by little<\/strong> or to update daily to obtain a much more reliable result in a shorter period of time<\/strong>. This allows us to better meet the goal timings, avoiding the pressure derived from last minute deliveries and offering higher quality results to our clients<\/strong>.<\/span><\/p>\n Another advantage of CI is found at the team members and individual levels. Since these practices are carried out in joint projects, the developers themselves are who will analyze the code, supporting each other. They themselves will have to learn different methods of integration and be forced to overcome day after day different errors or failures found in the code. This encourages communication between team members<\/strong>, and makes it much more enriching both individually and at the group or team level. And, as is logical, it also indirectly benefits the client, who enjoys a well-organized technical team and higher quality results.<\/strong><\/span><\/p>\n <\/p>\n<\/span>How is continuous integration applied?<\/b><\/span><\/h2>\n