<?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 La-Tech</title><link>https://la-tech.co/tags/jenkins/</link><description>Recent content in Jenkins on La-Tech</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Thu, 03 Dec 2020 00:00:00 +0000</lastBuildDate><atom:link href="https://la-tech.co/tags/jenkins/index.xml" rel="self" type="application/rss+xml"/><item><title>Jenkins status checks sans webhooks</title><link>https://la-tech.co/jenkins-status-checks/</link><pubDate>Thu, 03 Dec 2020 00:00:00 +0000</pubDate><guid>https://la-tech.co/jenkins-status-checks/</guid><description>Jenkins the once dominant CI/CD work horse has taken a back seat as of late. Not because it&amp;rsquo;s less powerful then its competition but because they have lowered the barrier to entry. One place where tools like Travis-CI, Circle-CI and Gitlab-CI excel at are ease of use.
I guess Gitlab is not in the cool kids club =/ A very basic need for most teams is the ability to block a feature branch from being merged that doesn&amp;rsquo;t meet certain requirements.</description></item></channel></rss>