<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Continuous Integration on Maarten on IT</title><link>https://maarten.mulders.it/categories/continuous-integration/</link><description>Recent content in Continuous Integration on Maarten on IT</description><generator>Hugo</generator><language>en-us</language><copyright>&amp;copy; 2013 - 2026 Maarten Mulders</copyright><lastBuildDate>Tue, 07 Jan 2025 12:55:20 +0100</lastBuildDate><atom:link href="https://maarten.mulders.it/categories/continuous-integration/index.xml" rel="self" type="application/rss+xml"/><item><title>Reduce Maven Plugin logging</title><link>https://maarten.mulders.it/2024/07/reduce-maven-plugin-logging/</link><pubDate>Tue, 16 Jul 2024 08:16:00 +0200</pubDate><guid>https://maarten.mulders.it/2024/07/reduce-maven-plugin-logging/</guid><description>&lt;p&gt;Sometimes, a Maven plugin logs more then you want it to.
I recently had this situation with a plugin that generated source code from specifications.
This plugin alone wrote over 22000 lines of output just to inform the user that it did what it had to do.
No errors or such, only confirming that it did its job.
Such superfluous output makes it hard for developers to focus on actual problems in their build.
It&amp;rsquo;s too easy to think &amp;ldquo;too long, didn&amp;rsquo;t read&amp;rdquo; (TL;DR) and hence miss the important bits.
So, it&amp;rsquo;s time to tame the plugin logging!&lt;/p&gt;</description></item><item><title>Building ASP.NET Core apps on CircleCI</title><link>https://maarten.mulders.it/2018/04/building-asp.net-core-apps-on-circleci/</link><pubDate>Mon, 02 Apr 2018 11:42:35 +0200</pubDate><guid>https://maarten.mulders.it/2018/04/building-asp.net-core-apps-on-circleci/</guid><description>&lt;p&gt;Recently, my co-worker &lt;a href="https://twitter.com/willem_meints"&gt;Willem&lt;/a&gt; pulled my attention to the &lt;a href="https://docs.microsoft.com/en-us/dotnet/standard/microservices-architecture/index"&gt;.NET Microservices. Architecture for Containerized .NET Applications&lt;/a&gt; e-book.
Although I have a strong background in Java and the Java platform, I started reading it, and soon I felt like trying it out.
But building software without having automated builds and tests is not the real thing, so that was the first thing I wanted to do.
I usually use &lt;a href="https://circleci.com/"&gt;CircleCI&lt;/a&gt; for that, but unfortunately they don&amp;rsquo;t seem to have an official guide for that.&lt;/p&gt;</description></item></channel></rss>