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

Plugins fail to deploy attached artifacts upon release

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      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.

        Attachments

        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

          Activity

          Hide
          drulli 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...

          Show
          drulli 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...
          Hide
          drulli 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] ------------------------------------------------------------------------
          
          Show
          drulli 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] ------------------------------------------------------------------------
          Hide
          drulli 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.

          Show
          drulli 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.
          Hide
          drulli Ulli Hafner added a comment -

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

          Show
          drulli Ulli Hafner added a comment - Ok, finally findbugs has been released. Seems that adding the memory options to maven did help.
          Hide
          drulli 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.

          Show
          drulli 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.

            People

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

              Dates

              Created:
              Updated:
              Resolved: