https://bugzilla.redhat.com/show_bug.cgi?id=1147899
--- Comment #3 from Alex abcoyle@gmail.com --- Some clarification regarding my previous comment: copying the settings.xml is not the change that makes the difference, the correct workaround is to exec Maven manually once, after the first Jenkins build has failed:
cd /var/lib/jenkins/workspace/<job-name> su -s /bin/bash -c "mvn clean" jenkins
After performing this workaround, I found that subsequent Jenkins builds will succeed.