<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CI/CD on Software Factory</title><link>/use/practices/ci/</link><description>Recent content in CI/CD on Software Factory</description><generator>Hugo</generator><language>en</language><atom:link href="/use/practices/ci/index.xml" rel="self" type="application/rss+xml"/><item><title>Continuous Integration</title><link>/use/practices/ci/continuous-integration/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/use/practices/ci/continuous-integration/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;a class="td-heading-self-link" href="#overview" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Continuous Integration (CI) is a software development practice that has revolutionized how teams
build and deliver software.&lt;/p&gt;
&lt;p&gt;At its core, CI involves frequently integrating code changes into a shared repository,
typically several times a day.&lt;/p&gt;
&lt;p&gt;Each integration is verified by an automated build and test process,
allowing teams to detect and address issues early in the development cycle.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Continuous Integration is a development practice where team members frequently integrate their work,
often daily, resulting in multiple integrations per day.&lt;/p&gt;</description></item><item><title>GitLab pipeline</title><link>/use/practices/ci/gitlab-ci-pipeline/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/use/practices/ci/gitlab-ci-pipeline/</guid><description>&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Keep Your Pipelines &lt;a href="https://fr.wikipedia.org/wiki/Idempotence" class="external-link" target="_blank" rel="noopener noreferrer"&gt;Idempotent&lt;/a&gt;
&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Keep Your Pipelines Fast&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Use Trusted Docker Images&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="test-job-commands-locally"&gt;Test Job Commands Locally&lt;a class="td-heading-self-link" href="#test-job-commands-locally" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;Before running job commands in GitLab, it&amp;rsquo;s beneficial to perform local tests.
This approach offers several advantages:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Detect and correct issues more efficiently.&lt;/li&gt;
&lt;li&gt;Minimize the chances of unexpected problems in GitLab.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;By focusing on local testing, you can ensure a smoother operation when implementing commands in
the GitLab environment.
If you need external services to run tests, you can use &lt;code&gt;docker-compose&lt;/code&gt; on your local environnement.&lt;/p&gt;</description></item></channel></rss>