Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-5037

Plugins fail to deploy attached artifacts upon release

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • plugin-proposals
    • None

      Apparently the "mvn release:perform" no longer deploys the sources, javadoc, nor the jar artifacts.

      See http://maven.glassfish.org/content/groups/public/org/jvnet/hudson/plugins/batch-task/1.9/ for example.

      This must be either a bug in the maven-hpi-plugin or a change in POM.

        1. findbugs.log
          62 kB
        2. output.log
          90 kB
        3. pmd.log
          30 kB
        4. pmd-release.log
          29 kB
        5. release.log
          188 kB
        6. release.ssh-slaves.log
          29 kB
        7. warnings-release.log
          54 kB

          [JENKINS-5037] Plugins fail to deploy attached artifacts upon release

          Ulli Hafner added a comment -

          Attached is the output of the release command for analysis-core 1.1.

          Ulli Hafner added a comment - Attached is the output of the release command for analysis-core 1.1.

          Ulli Hafner added a comment -

          Attached is the output of the release command for warnings 3.1.

          Ulli Hafner added a comment - Attached is the output of the release command for warnings 3.1.

          Ulli Hafner added a comment -

          Attached is the output of the release command for pmd 3.1.

          Ulli Hafner added a comment - Attached is the output of the release command for pmd 3.1.

          Ulli Hafner added a comment - - edited

          Added log file for the release of the remaining plug-ins. (checkstyle, dry, findbugs, tasks).

          Seems that the findbugs plugin has an out of memory error during upload:

          [INFO] [ERROR] FATAL ERROR
          [INFO] [INFO] ------------------------------------------------------------------------
          [INFO] [INFO] Java heap space
          [INFO] [INFO] ------------------------------------------------------------------------
          [INFO] [INFO] Trace
          [INFO] java.lang.OutOfMemoryError: Java heap space
          [INFO] 	at java.util.Arrays.copyOf(Arrays.java:2786)
          [INFO] 	at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94)
          [INFO] 	at sun.net.www.http.PosterOutputStream.write(PosterOutputStream.java:61)
          [INFO] 	at com.meterware.httpunit.MimeEncodedMessageBody$MimeEncoding.addFile(MimeEncodedMessageBody.java:144)
          [INFO] 	at com.meterware.httpunit.FileSubmitFormControl.addValues(FormControl.java:867)
          [INFO] 	at com.meterware.httpunit.WebForm.recordParameters(WebForm.java:499)
          [INFO] 	at com.meterware.httpunit.MimeEncodedMessageBody.writeTo(MimeEncodedMessageBody.java:59)
          [INFO] 	at com.meterware.httpunit.MessageBodyWebRequest.writeMessageBody(MessageBodyWebRequest.java:84)
          [INFO] 	at com.meterware.httpunit.MessageBodyWebRequest.completeRequest(MessageBodyWebRequest.java:97)
          [INFO] 	at com.meterware.httpunit.WebConversation.newResponse(WebConversation.java:60)
          [INFO] 	at com.meterware.httpunit.WebWindow.getResource(WebWindow.java:162)
          [INFO] 	at com.meterware.httpunit.WebWindow.getSubframeResponse(WebWindow.java:125)
          [INFO] 	at com.meterware.httpunit.WebWindow.getResponse(WebWindow.java:118)
          [INFO] 	at com.meterware.httpunit.WebWindow.sendRequest(WebWindow.java:107)
          [INFO] 	at com.meterware.httpunit.WebRequestSource.submitRequest(WebRequestSource.java:245)
          [INFO] 	at com.meterware.httpunit.WebRequestSource.submitRequest(WebRequestSource.java:224)
          [INFO] 	at com.meterware.httpunit.WebForm.doFormSubmit(WebForm.java:75)
          [INFO] 	at com.meterware.httpunit.WebForm.submit(WebForm.java:67)
          [INFO] 	at com.meterware.httpunit.WebForm.submit(WebForm.java:56)
          [INFO] 	at org.kohsuke.jnt.JNFileFolder$2.scrape(JNFileFolder.java:279)
          [INFO] 	at org.kohsuke.jnt.JNFileFolder$2.scrape(JNFileFolder.java:222)
          [INFO] 	at org.kohsuke.jnt.Scraper.run(Scraper.java:29)
          [INFO] 	at org.kohsuke.jnt.JNFileFolder._upload(JNFileFolder.java:222)
          [INFO] 	at org.kohsuke.jnt.JNFileFolder.uploadFile(JNFileFolder.java:302)
          [INFO] 	at org.jvnet.hudson.maven.plugins.hpi.UploadMojo.execute(UploadMojo.java:49)
          [INFO] 	at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
          [INFO] 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
          [INFO] 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
          [INFO] 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
          [INFO] 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
          [INFO] 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
          [INFO] 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
          [INFO] [INFO] ------------------------------------------------------------------------
          [INFO] [INFO] Total time: 9 minutes 8 seconds
          [INFO] [INFO] Finished at: Mon Dec 28 01:00:49 CET 2009
          [INFO] [INFO] Final Memory: 54M/63M
          [INFO] [INFO] ------------------------------------------------------------------------
          [INFO] ------------------------------------------------------------------------
          [ERROR] BUILD ERROR
          [INFO] ------------------------------------------------------------------------
          [INFO] Maven execution failed, exit code: '1'
          

          I will increase the memory and try again...

          Ulli Hafner added a comment - - edited Added log file for the release of the remaining plug-ins. (checkstyle, dry, findbugs, tasks). Seems that the findbugs plugin has an out of memory error during upload: [INFO] [ERROR] FATAL ERROR [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [INFO] Java heap space [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [INFO] Trace [INFO] java.lang.OutOfMemoryError: Java heap space [INFO] at java.util.Arrays.copyOf(Arrays.java:2786) [INFO] at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94) [INFO] at sun.net.www.http.PosterOutputStream.write(PosterOutputStream.java:61) [INFO] at com.meterware.httpunit.MimeEncodedMessageBody$MimeEncoding.addFile(MimeEncodedMessageBody.java:144) [INFO] at com.meterware.httpunit.FileSubmitFormControl.addValues(FormControl.java:867) [INFO] at com.meterware.httpunit.WebForm.recordParameters(WebForm.java:499) [INFO] at com.meterware.httpunit.MimeEncodedMessageBody.writeTo(MimeEncodedMessageBody.java:59) [INFO] at com.meterware.httpunit.MessageBodyWebRequest.writeMessageBody(MessageBodyWebRequest.java:84) [INFO] at com.meterware.httpunit.MessageBodyWebRequest.completeRequest(MessageBodyWebRequest.java:97) [INFO] at com.meterware.httpunit.WebConversation.newResponse(WebConversation.java:60) [INFO] at com.meterware.httpunit.WebWindow.getResource(WebWindow.java:162) [INFO] at com.meterware.httpunit.WebWindow.getSubframeResponse(WebWindow.java:125) [INFO] at com.meterware.httpunit.WebWindow.getResponse(WebWindow.java:118) [INFO] at com.meterware.httpunit.WebWindow.sendRequest(WebWindow.java:107) [INFO] at com.meterware.httpunit.WebRequestSource.submitRequest(WebRequestSource.java:245) [INFO] at com.meterware.httpunit.WebRequestSource.submitRequest(WebRequestSource.java:224) [INFO] at com.meterware.httpunit.WebForm.doFormSubmit(WebForm.java:75) [INFO] at com.meterware.httpunit.WebForm.submit(WebForm.java:67) [INFO] at com.meterware.httpunit.WebForm.submit(WebForm.java:56) [INFO] at org.kohsuke.jnt.JNFileFolder$2.scrape(JNFileFolder.java:279) [INFO] at org.kohsuke.jnt.JNFileFolder$2.scrape(JNFileFolder.java:222) [INFO] at org.kohsuke.jnt.Scraper.run(Scraper.java:29) [INFO] at org.kohsuke.jnt.JNFileFolder._upload(JNFileFolder.java:222) [INFO] at org.kohsuke.jnt.JNFileFolder.uploadFile(JNFileFolder.java:302) [INFO] at org.jvnet.hudson.maven.plugins.hpi.UploadMojo.execute(UploadMojo.java:49) [INFO] at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [INFO] Total time: 9 minutes 8 seconds [INFO] [INFO] Finished at: Mon Dec 28 01:00:49 CET 2009 [INFO] [INFO] Final Memory: 54M/63M [INFO] [INFO] ------------------------------------------------------------------------ [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Maven execution failed, exit code: '1' I will increase the memory and try again...

          Ulli Hafner added a comment - - edited

          I just tried to upgrade my plug-ins, but the PMD plug-in seems to be not available. Additionally, the download site also contains no PMD hpi file. However, the log file for PMD did not show an error. Any ideas?

          Is this a disk memory problem, PMD and findbugs are quite big plugins due to the included libraries?

          Ulli Hafner added a comment - - edited I just tried to upgrade my plug-ins, but the PMD plug-in seems to be not available. Additionally, the download site also contains no PMD hpi file. However, the log file for PMD did not show an error. Any ideas? Is this a disk memory problem, PMD and findbugs are quite big plugins due to the included libraries?

          Ulli Hafner added a comment -

          Hmm, I've just seen that the PMD release was 3.0 and not 3.1. Maybe the release went wrong due to the broken release process in november. Therefore the release number was used again. I'll re-try, too...

          Ulli Hafner added a comment - Hmm, I've just seen that the PMD release was 3.0 and not 3.1. Maybe the release went wrong due to the broken release process in november. Therefore the release number was used again. I'll re-try, too...

          Ulli Hafner added a comment -

          Hmm, now the release stops with the following message, I think I'll retry later from home:

          [INFO] [INFO] ------------------------------------------------------------------------
          [INFO] [ERROR] BUILD ERROR
          [INFO] [INFO] ------------------------------------------------------------------------
          [INFO] [INFO] Error deploying artifact: Connection failed: Unable to connect to https://svn.dev.java.net/svn/maven2-repository/trunk/repository/
          [INFO] 
          [INFO] svn: The specified baseline is not the latest baseline, so it may not be checked out.
          [INFO] svn: CHECKOUT of '/svn/maven2-repository/!svn/bln/1592032': 409 Conflict (https://svn.dev.java.net)
          [INFO] [INFO] ------------------------------------------------------------------------
          [INFO] [INFO] For more information, run Maven with the -e switch
          [INFO] [INFO] ------------------------------------------------------------------------
          [INFO] [INFO] Total time: 36 seconds
          [INFO] [INFO] Finished at: Mon Dec 28 11:35:07 CET 2009
          [INFO] [INFO] Final Memory: 52M/119M
          [INFO] [INFO] ------------------------------------------------------------------------
          

          Ulli Hafner added a comment - Hmm, now the release stops with the following message, I think I'll retry later from home: [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [ERROR] BUILD ERROR [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [INFO] Error deploying artifact: Connection failed: Unable to connect to https://svn.dev.java.net/svn/maven2-repository/trunk/repository/ [INFO] [INFO] svn: The specified baseline is not the latest baseline, so it may not be checked out. [INFO] svn: CHECKOUT of '/svn/maven2-repository/!svn/bln/1592032': 409 Conflict (https://svn.dev.java.net) [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [INFO] Total time: 36 seconds [INFO] [INFO] Finished at: Mon Dec 28 11:35:07 CET 2009 [INFO] [INFO] Final Memory: 52M/119M [INFO] [INFO] ------------------------------------------------------------------------

          Ulli Hafner added a comment -

          Tried again to release and now everything seems to work. Seems that this problem is related to some connection problems, I did not change anything in the pom.

          Ulli Hafner added a comment - Tried again to release and now everything seems to work. Seems that this problem is related to some connection problems, I did not change anything in the pom.

          Ulli Hafner added a comment -

          Ok, finally findbugs has been released. Seems that adding the memory options to maven did help.

          Ulli Hafner added a comment - Ok, finally findbugs has been released. Seems that adding the memory options to maven did help.

          Ulli Hafner added a comment -

          Ok, I checked the files and all jars seem to be present now. I added the new memory options to my .bashrc, so the next time everything should work automatically.

          Ulli Hafner added a comment - Ok, I checked the files and all jars seem to be present now. I added the new memory options to my .bashrc, so the next time everything should work automatically.

            drulli Ulli Hafner
            kohsuke Kohsuke Kawaguchi
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: