<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://wiki.bzz.ch/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://wiki.bzz.ch/feed.php">
        <title>BZZ - Modulwiki - en:modul:m324_aws:topics</title>
        <description></description>
        <link>https://wiki.bzz.ch/</link>
        <image rdf:resource="https://wiki.bzz.ch/_media/wiki/logo.png" />
       <dc:date>2026-05-18T09:21:51+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://wiki.bzz.ch/en/modul/m324_aws/topics/01?rev=1760527468&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.bzz.ch/en/modul/m324_aws/topics/02?rev=1762347329&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.bzz.ch/en/modul/m324_aws/topics/03?rev=1761043291&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.bzz.ch/en/modul/m324_aws/topics/04?rev=1761130362&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.bzz.ch/en/modul/m324_aws/topics/05?rev=1760528188&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.bzz.ch/en/modul/m324_aws/topics/06?rev=1760528132&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.bzz.ch/en/modul/m324_aws/topics/07?rev=1760529743&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.bzz.ch/en/modul/m324_aws/topics/08?rev=1765784630&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.bzz.ch/en/modul/m324_aws/topics/09?rev=1760530081&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.bzz.ch/en/modul/m324_aws/topics/10?rev=1767781589&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.bzz.ch/en/modul/m324_aws/topics/11?rev=1768036910&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://wiki.bzz.ch/_media/wiki/logo.png">
        <title>BZZ - Modulwiki</title>
        <link>https://wiki.bzz.ch/</link>
        <url>https://wiki.bzz.ch/_media/wiki/logo.png</url>
    </image>
    <item rdf:about="https://wiki.bzz.ch/en/modul/m324_aws/topics/01?rev=1760527468&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-10-15T11:24:28+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Introduction to DevOps</title>
        <link>https://wiki.bzz.ch/en/modul/m324_aws/topics/01?rev=1760527468&amp;do=diff</link>
        <description>Introduction to DevOps

Internal reference: topics/01-1.md



What is DevOps?

The term DevOps represents the combination of Development (Dev) and Operations (Ops). 
DevOps culture is a set of practices that reduce the barriers between developers, who want to innovate and deliver faster, and operations, who want to guarantee the stability of production systems and the quality of the system changes they make.
DevOps culture is also the</description>
    </item>
    <item rdf:about="https://wiki.bzz.ch/en/modul/m324_aws/topics/02?rev=1762347329&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-11-05T12:55:29+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Introduction to Jenkins</title>
        <link>https://wiki.bzz.ch/en/modul/m324_aws/topics/02?rev=1762347329&amp;do=diff</link>
        <description>Introduction to Jenkins

Internal reference: topics/02-1.md



What is Jenkins?

Jenkins is an open source automation server written in Java. With very active community-based support and a huge number of plugins, it is one of the most popular tools for implementing continuous integration and continuous delivery processes. Formerly known as Hudson, it was renamed after Oracle bought Hudson and decided to develop it as proprietary software. Jenkins was forked from Hudson but remained open source u…</description>
    </item>
    <item rdf:about="https://wiki.bzz.ch/en/modul/m324_aws/topics/03?rev=1761043291&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-10-21T10:41:31+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Jenkins architecture</title>
        <link>https://wiki.bzz.ch/en/modul/m324_aws/topics/03?rev=1761043291&amp;do=diff</link>
        <description>Jenkins architecture

Internal reference: topics/02-2.md



Master and agents

Jenkins server (master) delegates builds and execution tasks to agent (slave) instances. 

[Fig-01: Jenkins master-agent interaction]

Jenkins controller (master) is responsible for the following:

	*  Receiving build triggers (for example, after a commit to GitHub)</description>
    </item>
    <item rdf:about="https://wiki.bzz.ch/en/modul/m324_aws/topics/04?rev=1761130362&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-10-22T10:52:42+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Introduction to Jenkins pipeline</title>
        <link>https://wiki.bzz.ch/en/modul/m324_aws/topics/04?rev=1761130362&amp;do=diff</link>
        <description>Introduction to Jenkins pipeline

Internal reference: topics/03-1.md



Introduction

A pipeline is a sequence of automated operations that usually represents a part of the software delivery and quality assurance process. It can be seen as a chain of scripts that provide the following additional benefits:</description>
    </item>
    <item rdf:about="https://wiki.bzz.ch/en/modul/m324_aws/topics/05?rev=1760528188&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-10-15T11:36:28+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Jenkins&#039; Pipeline syntax</title>
        <link>https://wiki.bzz.ch/en/modul/m324_aws/topics/05?rev=1760528188&amp;do=diff</link>
        <description>Jenkins&#039; Pipeline syntax

Internal reference: topics/03-2.md



Pipeline syntax

In this course we use the declarative syntax that is recommended for all new projects. The other options are a Groovy-based DSL and XML (created through the web interface).
The declarative syntax was designed to make it as simple as possible to understand the pipeline, even by people who do not write code on a daily basis. This is why the syntax is limited only to the most important keywords.</description>
    </item>
    <item rdf:about="https://wiki.bzz.ch/en/modul/m324_aws/topics/06?rev=1760528132&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-10-15T11:35:32+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Jenkins&#039; Commit Pipeline</title>
        <link>https://wiki.bzz.ch/en/modul/m324_aws/topics/06?rev=1760528132&amp;do=diff</link>
        <description>Jenkins&#039; Commit Pipeline

Internal reference: topics/03-3.md



Introduction

The most basic continuous integration process is called a commit pipeline. This classic phase, as its name indicates, starts with commit (or push in Git) to the main repository and results in a report about the build success or failure. Since it runs after each change in the code, the build should take no more than 5 minutes and should consume a reasonable amount of resources. The commit phase is always the starting po…</description>
    </item>
    <item rdf:about="https://wiki.bzz.ch/en/modul/m324_aws/topics/07?rev=1760529743&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-10-15T12:02:23+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Docker in a Docker (DinD)</title>
        <link>https://wiki.bzz.ch/en/modul/m324_aws/topics/07?rev=1760529743&amp;do=diff</link>
        <description>Docker in a Docker (DinD)

Internal reference: topics/04-1.md



Introduction

Here are a few use cases to run docker inside a docker container.

	*  One potential use case for docker in docker is for the CI/CD pipeline, where you need to build and push docker images to a container registry after a successful code build.</description>
    </item>
    <item rdf:about="https://wiki.bzz.ch/en/modul/m324_aws/topics/08?rev=1765784630&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-12-15T07:43:50+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>How to Use Conditional Constructs in Jenkins Pipeline</title>
        <link>https://wiki.bzz.ch/en/modul/m324_aws/topics/08?rev=1765784630&amp;do=diff</link>
        <description>How to Use Conditional Constructs in Jenkins Pipeline

Internal reference: topics/05-1.md



Introduction

Effective Jenkins pipelines rely heavily on conditional constructs to control the execution flow. Using these constructs, we get the flexibility to change the flow of execution based on dynamic criteria, such as environment variables, results from previous steps, or any other condition.
The declarative nature of writing pipelines in Jenkins allows us to define the pipeline jobs in a simplif…</description>
    </item>
    <item rdf:about="https://wiki.bzz.ch/en/modul/m324_aws/topics/09?rev=1760530081&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-10-15T12:08:01+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>What is code coverage?</title>
        <link>https://wiki.bzz.ch/en/modul/m324_aws/topics/09?rev=1760530081&amp;do=diff</link>
        <description>What is code coverage?

Internal reference: topics/06-1.md



Introduction

Code coverage is a software testing metric that determines the number of lines of code that is successfully validated under a test procedure. This metric helps to analyze how comprehensively a software is verified.
Developing enterprise-grade software products is the ultimate goal of any software company. However, to accomplish this goal, companies have to ensure that the software they develop meets all the essential qua…</description>
    </item>
    <item rdf:about="https://wiki.bzz.ch/en/modul/m324_aws/topics/10?rev=1767781589&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-01-07T10:26:29+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Code coverage with Jest</title>
        <link>https://wiki.bzz.ch/en/modul/m324_aws/topics/10?rev=1767781589&amp;do=diff</link>
        <description>Code coverage with Jest

Internal reference: topics/06-2.md



Introduction

Popular JavaScript frameworks can use Facebook’s Jest to perform unit tests.
Jest has the Coverage Report feature that allows us to check if our code covers all lines of the files we choose by generating an</description>
    </item>
    <item rdf:about="https://wiki.bzz.ch/en/modul/m324_aws/topics/11?rev=1768036910&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-01-10T09:21:50+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Code coverage with SonarQube</title>
        <link>https://wiki.bzz.ch/en/modul/m324_aws/topics/11?rev=1768036910&amp;do=diff</link>
        <description>Code coverage with SonarQube

Internal reference: topics/06-3.md



Introduction

SonarQube is a Java-based open-source code coverage tool. Beside running code coverage, it allows static code analysis to evaluate the reliability and security of a program. With</description>
    </item>
</rdf:RDF>
