<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Continuous Delivery on Martin Ahrer</title><link>https://www.martinahrer.at/tags/continuous-delivery/</link><description>Recent content in Continuous Delivery on Martin Ahrer</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 03 Aug 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://www.martinahrer.at/tags/continuous-delivery/index.xml" rel="self" type="application/rss+xml"/><item><title>Detect and alert common vulnerabilities and exposures (CVE) in 3rd-party dependencies</title><link>https://www.martinahrer.at/2022/08/03/detect-and-alert-common-vulnerabilities-and-exposures-cve-in-3rd-party-dependencies/</link><pubDate>Wed, 03 Aug 2022 00:00:00 +0000</pubDate><guid>https://www.martinahrer.at/2022/08/03/detect-and-alert-common-vulnerabilities-and-exposures-cve-in-3rd-party-dependencies/</guid><description>&lt;div class="paragraph">
&lt;p>Using 3rd-party libraries makes developer’s lives so much easier but can turn them into a nightmare when they are unmanaged and we don’t have a good understanding what is being used in a project or even a larger organization.&lt;/p>
&lt;/div>
&lt;div class="paragraph">
&lt;p>A few months ago we have seen quite a few popular frameworks widely used in many software products being hit by severe CVE (common vulnerabilities and exposures).&lt;/p>
&lt;/div></description></item><item><title>Continuous delivery infrastructure as code</title><link>https://www.martinahrer.at/2017/05/10/continuous-delivery-infrastructure-as-code/</link><pubDate>Wed, 10 May 2017 00:00:00 +0000</pubDate><guid>https://www.martinahrer.at/2017/05/10/continuous-delivery-infrastructure-as-code/</guid><description>&lt;div id="preamble">
&lt;div class="sectionbody">
&lt;div class="paragraph">
&lt;p>This is part 1 of a series of posts covering Docker in a Continuous Delivery environment.&lt;/p>
&lt;/div>
&lt;div class="paragraph">
&lt;p>Today I’m showing how simple it is to setup a continuous delivery build pipeline infrastructure using Docker.
In an upcoming post we will look at Jenkins pipeline as code creating Docker images and running integration tests against Docker containers.
The series will close with an article explaining how we can move all containers built throughout this series of posts in a Docker swarm environment.&lt;/p>
&lt;/div></description></item></channel></rss>