Do you a maven job type, or a freestyle one. If the first, then you might want to try using a freestyle job instead as a first debugging step.
My 2 cents Le 6 juin 2016 1:28 PM, "Christa Reitsamer" <[email protected]> a écrit : > I'm configuring Jenkins (2.6) with Subversion (TortoiseSVN 1.9.4), Maven > (3.3.9), JDK 1.8.0_91 and Artifactory (4.7.6). > Till yesterday we used an older version of Artifactory on an other, > separated server. Yesterday I installed the new Artifactory and imported > the whole system information from the old one. Now we have installed all on > the same Windows Server with actual versions. > > But my problem is, that it seems that I always check out just the same old > codeversion for release build. > > For the explicit Job I use JDK 1.8, Subversion with "Always check out a > fresh copy" (seems that "use Update as much as possible" doesn't work > correct?!) > > Maven goals for release buid: clean install -B -Dresume=false > release:prepare release:perform -Darguments="-Dmaven.javadoc.skip=true" > > If I start the build, everything is OK: > BUILD SUCCESS --> Checkout seems to be OK (Revision is correct), Parsing > POM: Maven executes POM which contains correct root-POM version, correct > SNAPSHOT version, correct SNV-folder etc. and using correct settings.xml > > If I start the release build: > > The build is also successful but when the release part starts, Jenkins > tries building another, old release. > > In the console output I see it starts with executing goals "deploy". At > that point Jenkins ALWAYS tries to build the old release 2.1 (actual 2.2.22 > and higher). > > Therefore Jenkins downloads and uploads data from the old artifactory > (without changes). > > If I stop the old artifactory I get the build error: > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-release-plugin:2.5.3:perform (default-cli) > on project bev-web-base: Maven execution failed, exit code: '1' -> [Help 1] > > [ERROR] > > But I don't understand why Jenkins always tries to build the release 2.1. > > I tried changing the maven release plugin from 2.5.3 to 2.5.2, but that > has no effect. I also tried to delete all checkouts from C:\Program Files > (x86)\Jenkins\jobs\Jobname\workspace\ and my local repository but all my > changes are effectless. > > I have no idea where I should change the configuration to build the actual > release... And I have no idea where Jenkins gets the information of release > 2.1. > > (the configuration for the new artifactory ist actual in settings.xml and > root POM) > Can someone help me please?! > > (Sorry for my english, i hope you unterstand what i'm trying to say) > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/58cc267f-1e0a-45ec-aef5-63244fb5e0f5%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/58cc267f-1e0a-45ec-aef5-63244fb5e0f5%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS41yuwg_RobqJPjcEB8VD4gkByo-KjFD%3D6C6xYC0Sz%2BKQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
