<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>ci/cd on Why did IT fail</title><link>https://www.why-did-it.fail/tags/ci/cd/</link><description>Recent content in ci/cd on Why did IT fail</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Copyright © 2026 Dominik Textoris (formerly Zorgnotti). All Rights Reserved.</copyright><atom:link href="https://www.why-did-it.fail/tags/ci/cd/index.xml" rel="self" type="application/rss+xml"/><item><title>Automating vSphere template builds with a pipeline - IV</title><link>https://www.why-did-it.fail/blog/2020-05-automating-templates-part4/</link><pubDate>Tue, 04 Feb 2020 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2020-05-automating-templates-part4/</guid><description>This is the fourth part in a multi-part series about the automation of VMware vSphere template builds. A template is a pre-installed virtual machine that acts as master image for cloning virtual machines from it. In this series I am describing how to get started on automating the process. As I am writing these blog post while working on the implementation some aspects may seem &amp;ldquo;rough around the edges&amp;rdquo;.
Part 1: Overview/Motivation Part 2: Building a pipeline for a MVP Part 3: An overview of packer Part 4: Concourse elements and extending the pipeline The focus in this part are the concourse basics.</description><enclosure url="https://www.why-did-it.fail/blog/2020-05-automating-templates-part4/feature.png" length="40551" type="image/png"/></item><item><title>Automating vSphere template builds with a pipeline - III</title><link>https://www.why-did-it.fail/blog/2020-05-automating-templates-part3/</link><pubDate>Thu, 23 Jan 2020 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2020-05-automating-templates-part3/</guid><description>This is the third part in a multi-part series about the automation of VMware vSphere template builds. A template is a pre-installed virtual machine that acts as master image for cloning virtual machines from it. In this series I am describing how to get started on automating the process. As I am writing these blog post while working on the implementation some aspects may seem &amp;ldquo;rough around the edges&amp;rdquo;.
Part 1: Overview/Motivation Part 2: Building a pipeline for a MVP Part 3: An overview of packer Part 4: Concourse elements and extending the pipeline If all went well, part 2 left you with a functional Ubuntu template.</description></item><item><title>Automating vSphere template builds with a pipeline - II</title><link>https://www.why-did-it.fail/blog/2020-05-automating-templates-part2/</link><pubDate>Tue, 21 Jan 2020 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2020-05-automating-templates-part2/</guid><description>This is the second part in a multi-part series about the automation of VMware vSphere template builds. A template is a pre-installed virtual machine that acts as master image for cloning virtual machines from it. In this series I am describing how to get started on automating the process. As I am writing these blog post while working on the implementation some aspects may seem &amp;ldquo;rough around the edges&amp;rdquo;.
Part 1: Overview/Motivation Part 2: Building a pipeline for a MVP Part 3: An overview of packer Part 4: Concourse elements and extending the pipeline This part will focus on getting you started with a minimum viable product by building a single Ubuntu 18.</description><enclosure url="https://www.why-did-it.fail/blog/2020-05-automating-templates-part2/feature.png" length="56539" type="image/png"/></item><item><title>Automating vSphere template builds with a pipeline - I</title><link>https://www.why-did-it.fail/blog/2020-05-automating-templates-part1/</link><pubDate>Sun, 19 Jan 2020 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2020-05-automating-templates-part1/</guid><description>This is a multi-part series about the automation of VMware vSphere template builds. A template is a pre-installed virtual machine that acts as master image for cloning virtual machines from it. In this series I am describing how to get started on automating the process. As I am writing these blog post while working on the implementation some aspects may seem &amp;ldquo;rough around the edges&amp;rdquo;.
Part 1: Overview/Motivation Part 2: Building a pipeline for a MVP Part 3: An overview of packer Part 4: Concourse elements and extending the pipeline If you want to know more about the topic here is an awesome blog series about automated template management from Eric Lee - many thanks to Timo Sugliani for the recommendation.</description><enclosure url="https://www.why-did-it.fail/blog/2020-05-automating-templates-part1/feature.png" length="55278" type="image/png"/></item></channel></rss>