<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ci/Cd on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/tags/ci/cd/</link><description>Recent content in Ci/Cd on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 12 May 2026 07:00:00 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/tags/ci/cd/index.xml" rel="self" type="application/rss+xml"/><item><title>Stop Writing YAML: How to Define, Test, and Deploy Your Cloud in Pure Java</title><link>https://javapro-en.svenruppert.com/stop-writing-yaml-how-to-define-test-and-deploy-your-cloud-in-pure-java/</link><pubDate>Tue, 12 May 2026 07:00:00 +0000</pubDate><guid>https://javapro-en.svenruppert.com/stop-writing-yaml-how-to-define-test-and-deploy-your-cloud-in-pure-java/</guid><description>&lt;h2 id="1-introduction"&gt;&lt;strong&gt;1. Introduction&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;As Java developers, we apply rigorous engineering practices to application code: type safety, unit testing, refactoring, code review. Then we switch to deploying that code and write hundreds of lines of YAML, accepting the lack of expressiveness, missing abstractions, and missing flexibility as the cost of doing business. Or worse, we log into the cloud console and click our way through to the deployment.&lt;/p&gt;
&lt;p&gt;This article explores an alternative: defining cloud infrastructure in Java, with the same tools and practices we use for application code. We&amp;rsquo;ll build a working example, a Java service deployed on AWS, covering the full lifecycle from resource definition through testing to CI/CD. While this example uses Quarkus, the infrastructure patterns demonstrated here apply equally for Spring Boot, Jakarta EE, or any other containerized Java framework. The companion code is available at &lt;a href="https://github.com/wlami/stop-writing-yaml-javapro"&gt;github.com/wlami/stop-writing-yaml-javapro&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>The AI Mona Lisa Challenge: Precision and Security Adjustments for Your CI/CD Pipeline</title><link>https://javapro-en.svenruppert.com/the-ai-mona-lisa-challenge-precision-and-security-adjustments-for-your-ci-cd-pipeline/</link><pubDate>Thu, 21 Nov 2024 12:22:47 +0000</pubDate><guid>https://javapro-en.svenruppert.com/the-ai-mona-lisa-challenge-precision-and-security-adjustments-for-your-ci-cd-pipeline/</guid><description>&lt;p&gt;&lt;em&gt;&amp;ldquo;Mona Lisa, Mona Lisa, men have named you; you&amp;rsquo;re so like the lady with the mystic smile.&amp;rdquo;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Last time, I finished a &lt;a href="https://javapro.io/2024/10/17/are-ai-coding-tools-worth-it-part-1/"&gt;set of articles&lt;/a&gt; about using AI coding tools.  In the end, my conclusion was that the tools can help greatly but that right now,  using them to generate whole programs was pushing the envelope.  As helpers, as pseudo-pair-programmers,  the tools can offer great value and make you more productive.  However, it’s essential to understand that this process works because of the interaction between humans and AI.  Without the steering and a continuous mix of rejection and acceptance,  the AI can’t learn how to respond correctly.  &lt;/p&gt;</description></item></channel></rss>