Hi, Thanks! I noticed that the failed build had left the release.properties and pom.xml.releaseBackup files remaining, even though the build was in GitHub. It kept checking out the code from 1.1 even though I had made changes. Removing those files allowed me to get the checkout from the current version and it fixed one issue. Right now I have <findbugs.failOnError>false</findbugs.failOnError> in my pom.xml, which prevents it from failing to that error. I will try remove those tags and actually fix the problem now, that I have been able to fix the 1.1 clinging problem.
Aleksi Simell DevOps Consultant Eficode Ltd aleksi.sim...@eficode.com +358 400708005 On 26 July 2016 at 22:55, Jesse Glick <jgl...@cloudbees.com> wrote: > mvn release:rollback release:clean > > Forget about 1.1, move on. > > Use `mvn clean compile findbugs:findbugs` to look for violations locally. > > Use the newest available (2.x) parent POM, so that problems like this > will be caught during `prepare`, so that the `perform` phase does not > fail and leave a mess. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr038R9PXVJ9%2B1BLMfKJZvOFiAvmffdjC2kb2kUEzvYRwQ%40mail.gmail.com > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAEhvePUWxxHvC5C%2B7TtmXiG9cshdjDTZt%2BUtxvzmZYGcQf6UKA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
