Keeping your dependencies up to date is not the funniest part of a project dev process. Especially if the dependencies list becomes long. However, it is crucial to keep your dependencies as possible close to the up-to-date versions available in order to benefit from the latest upgrades (such as bug fixes). The longer you wait, the harder the upgrade will be.
So what if you receive an email every week to inform your team about the last version available of your projects dependencies? Some tools like Lint (or other static code analyzers) already provide such features, but as long as you don’t keep an eye on their reports you will not be warned about new versions.
In this quick tutorial we will setup a Jenkins job running a gradle plugin as a task in order to receive something like this by email:
The following dependencies have later milestone versions:
– com.android.support.test.espresso:espresso-core [2.0 -> 2.2.1]
– com.facebook.android:facebook-android-sdk [3.23.1 -> 4.8.2]
– com.fasterxml.jackson.core:jackson-annotations [2.5.3 -> 2.7.0-rc1]
– com.fasterxml.jackson.core:jackson-core [2.5.3 -> 2.7.0-rc1]
– com.fasterxml.jackson.core:jackson-databind [2.5.3 -> 2.7.0-rc1]