Sooner or later your CI server will became very busy, and your frustration will grow because of increasing wait time for each build. One thing you can do to improve the situation is to avoid running jobs when there is no need to do so.
I use Jenkins + Maven + SVN in this example, but you can use this "tricks" also when using different technologies - Gradle, Git etc.
Oh, a failed test again! And not on your local machine but on the CI server! What to do, oh, what to do?!
Problem: growing number of our own released artifacts (JARs/WARs) in our Artifactory. Solution: regular cleaning. This post explains how.
While installing Jenkins 1.486 on Ubuntu 12.10 server (64bit) with Java 7u9 I had two issues with libXrender.so.1 and libXtst.so.6 when running the first Maven build. I solved them and this post contains the solution.
This is a continuation of my mumblings about useful Jenkins plugins (see the first post here: http://kaczanowscy.pl/tomek/2012-05/recommended-jenkins-plugins). As we progress towards continuous delivery I learn a lot about new plugins.
Want to have always the latest documentation and database schema available? Then build it on your CI!
That is pretty cool that your CI polls SCM every minute to build and tests your code instantly. However, you still need a nightly build. Read why.