Hi Federico, Are you certain the package is damaged only after being deployed? I trust that you've compared the checksums of the produced artifact that's archived by Maven/Jenkins and the checksums of the artifact that's deployed? Perhaps you've got some sort of proxy or firewall between Jenkins and Artifactory that might alter the artifact on the way? or maybe network issues?
Cheers, Noam On May 9, 5:32 pm, Federico Paolantoni <[email protected]> wrote: > Dear List > i'm having big troubles with jenkins and artifactory: > Jenkins version 1.477.1 running on tomcat. > > Artifactory 2.6.0 running on tomcat with postgresql. > Maven 3.0.2 > Jdk 1.6.0_30-b12 > artifactory plugin: > 2.0.7<http://hqldvtcdrci1.hq.un.fao.org:8080/jenkins/pluginManager/plugin/a...> > > Actually even if the build run with succes, and the jar is produced... the > uploaded package is broken. > > How can i fix this issue? > Where should i find the log about this? > > This is a big issue for us, because the application deployed on all > environments dev, test, qa, prod are under controlo of Jenkins-ci. > Now we're stopped to find the solution to this issue! > > Thank you
