<?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 batmat.net</title>
		<link>https://batmat.net/tags/jenkins/</link>
		<description>Recent content in jenkins on batmat.net</description>
		<generator>Hugo</generator>
		<language>fr-FR</language>
		
		
		
		
			<lastBuildDate>Fri, 07 Sep 2018 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://batmat.net/tags/jenkins/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>How to run and upgrade Jenkins using the official Docker image</title>
				<link>https://batmat.net/2018/09/07/how-to-run-and-upgrade-jenkins-using-the-official-docker-image/</link>
				<pubDate>Fri, 07 Sep 2018 00:00:00 +0000</pubDate>
				<guid>https://batmat.net/2018/09/07/how-to-run-and-upgrade-jenkins-using-the-official-docker-image/</guid>
				
				<description> For some time now, I’ve been trying to follow and answer questions arising in the official Git repository for the Docker image of Jenkins.&#xA;I have especially been trying to encourage people to move away from using bind mounts [1] and prefer volumes instead.&#xA;Running Docker Containers Ideally, you never restart a container. You just start a new one from the same (or another) image.&#xA;Anything you want to keep has to be in the declared volume(s), that is all you need.&#xA;</description>
			</item>
			<item>
				<title>Do not run your tests in Continuous Integration with the root user</title>
				<link>https://batmat.net/2017/01/30/do-not-run-your-tests-in-continuous-integration-with-the-root-user/</link>
				<pubDate>Mon, 30 Jan 2017 00:00:00 +0000</pubDate>
				<guid>https://batmat.net/2017/01/30/do-not-run-your-tests-in-continuous-integration-with-the-root-user/</guid>
				
				<description> I was working recently on diagnosing unexpected tests failures that were only happening on our brand new Jenkins environment, and weren’t happening on the previous one. To provide some context, we now run a majority of things in one shot Docker containers, and that helped reveal an interested issue.&#xA;The offending code We have a test to check our code behaviour if a file we need to backup is readable or not. It was roughly like the following:&#xA;</description>
			</item>
	</channel>
</rss>
