Configure a CI build for each commit

Monday, February 5, 2018

By default in TFS/VSTS, the CI build configuration is used to trigger a build after each push. Additionally there is a option to "batch changes" (queue a build with all the changes since the last build instead of queue a build for each push). However there are some cases where you want to build each introduced commit separately. It's true that there is no way to do it automatically OOB, but in this post I want to share a way to achieve it with a little creativity (and code).   The Idea Create two different build definitions: - Listener Definition: Catch every push,...

Jenkins “Poll SCM” the Nightmare for Performance

Tuesday, January 24, 2017

How many of us have ever used the "Poll SCM" option in our Jenkins jobs? It’s very easy to simply say to our job "hey can you please verify every X time my repository and trigger the job only in case there are any changes" At first glance it’s a simple, quick and harmless way. And the most important, it’s an easy method and works well. However, have we ever wondered what this represents for our server? What is the cost of this "comfort"? Probably not, what is sure is that every time that the server get slow we quickly complain and...
no comments