<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Jenkins on Janik von Rotz</title>
    <link>https://janikvonrotz.ch/tags/jenkins/</link>
    <description>Recent content in Jenkins on Janik von Rotz</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 11 Apr 2024 14:15:28 +0200</lastBuildDate>
    <atom:link href="https://janikvonrotz.ch/tags/jenkins/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Build and deploy Odoo with and without Jenkins</title>
      <link>https://janikvonrotz.ch/2024/04/11/build-and-build-odoo-with-and-without-jenkins/</link>
      <pubDate>Thu, 11 Apr 2024 14:15:28 +0200</pubDate>
      <guid>https://janikvonrotz.ch/2024/04/11/build-and-build-odoo-with-and-without-jenkins/</guid>
      <description>&lt;p&gt;Jenkins is a popular but outdated CI/CD system. Compared to modern CI/CD systems such as GitHub Actions or GitLab Workflows, Jenkins does not deliver on containerization. As Docker containers are high in demand for building and hosting applications Jenkins has to go some extra miles. Nonetheless, Jenkins is yet the only self-hostable feature-rich CI/CD solution. For a project I went with Jenkins to deploy a multi-stage Odoo environment.&lt;/p&gt;&#xA;&lt;p&gt;In this post I would like to present the main parts of the final project such as the Docker setup or the Jenkins pipeline. An important goal was that the deployment can be done without Jenkins.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
