> On Jan 22, 2018, at 3:20 PM, Gary Gregory <garydgreg...@gmail.com> wrote: > > On Mon, Jan 22, 2018 at 3:14 PM, Ralph Goers <ralph.go...@dslextreme.com> > wrote: > >> I started to read it but it is too long. To be honest I would love it if >> I could just run the release from Jenkins. Unfortunately, that would >> require someone’s code signing key which would be a bit problematic to >> install on a shared server. In addition, I am a bit paranoid about making >> sure the build is going to work before starting it. We have lots of cases >> where the build works on our machines and fails in Jenkins, or vice versa. >> And the Jenkins build seems to fail 50% of them time anyway. >> > > What used to make the Jenkins build fail a lot was the log4j-osgi module > tests. I fixed that last week. Jenkins still does randomly fail > uploading/downloading files though. Nothing we can do about that one.
I’m not really sure why Jenkins is doing that. If we wanted the files to be deployed then the build should be using “mvn deploy” instead of “mvn install”. The major difference is that Jenkins only deploys after the whole build succeeds whereas Maven will deploy as each module succeeds. But Jenkins is also deploying modules that have the deploy goal disabled. Ralph
