Skip to content
Snippets Groups Projects
Commit 43cb12ed authored by Bot's avatar Bot Committed by TakiBot
Browse files

Added chapter 03-ansible

parent b534f18d
No related branches found
No related tags found
No related merge requests found
Pipeline #102997 passed
......@@ -584,8 +584,8 @@
<h1 id="discover-github">Discover Github</h1>
<div class="admonition note">
<p class="admonition-title">Note</p>
<div class="admonition check">
<p class="admonition-title">Check</p>
<p>Checkpoint: do a commit and call us to check your results (don’t stay blocked on a checkpoint if we are busy, we can check ⅔ checkpoints at the same time) </p>
</div>
<div class="admonition question">
......
......@@ -763,19 +763,16 @@
<p><img alt="github_actions_3" src="../assets/github_actions_3.png" /></p>
<div class="admonition check">
<p class="admonition-title">Check</p>
</div>
<p>First CI with backend test !</p>
<div class="admonition question">
<p class="admonition-title">Question</p>
<p>2-2 Document your Github Actions configurations.</p>
<p>First CI with backend test !
Document your Github Actions configurations by making a commit (that includes comments in the code). </p>
</div>
<h3 id="first-steps-into-the-cd-world">First steps into the CD World</h3>
<p>Here we are going to configure the Continuous Delivery of our project. Therefore, the main goal will be to create and save a docker image containing our application on the Docker Hub every time there is a commit on a main branch.</p>
<p>As you probably already noticed, you need to log in to docker hub to perform any publication. However, you don’t want to publish your credentials on a public repository (it is not even a good practise to do it on a private repository). Fortunately, <strong>GitHub</strong> allows you to create secured environment variables.</p>
<p>1- Add your docker hub credentials to the environment variables in <strong>GitHub Actions</strong> (and let them secured).</p>
<div class="admonition note">
<p class="admonition-title">Note</p>
<p>Secured Variables, why?</p>
<div class="admonition question">
<p class="admonition-title">Question</p>
<p>2-2 For what purpose do we need to use secured variables ?</p>
</div>
<p>Now that you added them, you can freely declare them and use them inside your <strong>GitHub Actions</strong> pipeline. </p>
<p><img alt="github_actions_4" src="../assets/github_actions_4.png" /></p>
......@@ -806,10 +803,10 @@
<a id="__codelineno-3-23" name="__codelineno-3-23" href="#__codelineno-3-23"></a><span class="w"> </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">Build image and push httpd</span>
<a id="__codelineno-3-24" name="__codelineno-3-24" href="#__codelineno-3-24"></a><span class="w"> </span><span class="c1"># DO the same for httpd</span>
</code></pre></div>
<div class="admonition note">
<p class="admonition-title">Note</p>
<p>Why did we put <strong>needs: build-and-test-backend</strong> on this job? Maybe try without this and you will see!</p>
<div class="admonition question">
<p class="admonition-title">Question</p>
</div>
<p>2-3 Why did we put <strong>needs: build-and-test-backend</strong> on this job? Maybe try without this and you will see!</p>
<p>OK your images are built but not yet published on <a href="https://hub.docker.com/" target="_blank">dockerhub</a>.</p>
<p>3- Publish your docker images when there is a commit on the main branch.</p>
<p>Don’t forget to do a docker login and to put your credentials on secrets!</p>
......@@ -830,7 +827,7 @@
<p>Do the same for other containers.</p>
<div class="admonition question">
<p class="admonition-title">Question</p>
<p>2-3 For what purpose do we need to push docker images?</p>
<p>2-4 For what purpose do we need to push docker images?</p>
</div>
<p>Now you should be able to find your docker images on your docker repository.</p>
<div class="admonition check">
......@@ -857,11 +854,8 @@
<p><img alt="sonarcloud_3" src="../assets/sonarcloud_3.png" /></p>
<div class="admonition check">
<p class="admonition-title">Check</p>
<p>Working quality gate.</p>
</div>
<div class="admonition question">
<p class="admonition-title">Question</p>
<p>2-4 Document your quality gate configuration.</p>
<p>Working quality gate.
Document your quality gate configuration by making a commit (that includes comments in the code).</p>
</div>
<p>Well done buddies, you’ve created your very first Quality Gate! Yay!</p>
<h2 id="going-further-split-pipelines">Going further: Split pipelines</h2>
......
......@@ -516,8 +516,8 @@
<h1 id="discover-ansible">Discover Ansible</h1>
<div class="admonition note">
<p class="admonition-title">Note</p>
<div class="admonition check">
<p class="admonition-title">Check</p>
<p>Checkpoint: do a commit and call us to check your results (don’t stay blocked on a checkpoint if we are busy, we can check ⅔ checkpoints at the same time) </p>
</div>
<div class="admonition question">
......
Source diff could not be displayed: it is too large. Options to address this: view the blob.
No preview for this file type
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment