even mvn deploy does not work.. Is there something wrong with my jenkins-ci account (philrumble) ?
On Fri, Oct 26, 2012 at 10:05 AM, Phil Rumble <[email protected]>wrote: > Ok, I've fixed that issue. firewall was in the way.. > > ho Hum.. onto the next issue > > This is the current error I get. btw I have the same username & passwd for > github and jenkins. > > > [INFO] Uploading: > http://maven.jenkins-ci.org:8081/content/repositories/releases/com/ibm/LotusConnectionsPlugin/1.8/LotusConnectionsPlugin-1.8.pom > [INFO] 3 KB > [INFO] > [INFO] [INFO] > ------------------------------------------------------------------------ > [INFO] [INFO] BUILD FAILURE > [INFO] [INFO] > ------------------------------------------------------------------------ > [INFO] [INFO] Total time: 2:06.246s > [INFO] [INFO] Finished at: Fri Oct 26 10:02:58 WST 2012 > [INFO] [INFO] Final Memory: 47M/112M > [INFO] [INFO] > ------------------------------------------------------------------------ > [INFO] [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.5:deploy (default-deploy) on > project LotusConnectionsPlugin: Failed to deploy artifacts: Could not > transfer artifact com.ibm:LotusConnectionsPlugin:hpi:1.8 from/to > maven.jenkins-ci.org ( > http://maven.jenkins-ci.org:8081/content/repositories/releases): Failed > to transfer file: > http://maven.jenkins-ci.org:8081/content/repositories/releases/com/ibm/LotusConnectionsPlugin/1.8/LotusConnectionsPlugin-1.8.hpi. > Return code is: 401 -> [Help 1] > [INFO] [ERROR] > [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven > with the -e switch. > [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug > logging. > [INFO] [ERROR] > [INFO] [ERROR] For more information about the errors and possible > solutions, please read the following articles: > [INFO] [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 2:19.169s > [INFO] Finished at: Fri Oct 26 10:02:58 WST 2012 > [INFO] Final Memory: 10M/81M > [INFO] > ------------------------------------------------------------------------ > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-release-plugin:2.0-beta-9:perform > (default-cli) on project LotusConnectionsPlugin: Maven execution failed, > exit code: '1' -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-release-plugin:2.0-beta-9:perform > (default-cli) on project LotusConnectionsPlugin: Maven execution failed, > exit code: '1' > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) > Caused by: org.apache.maven.plugin.MojoExecutionException: Maven execution > failed, exit code: '1' > at > org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:133) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > ... 19 more > Caused by: org.apache.maven.shared.release.ReleaseExecutionException: > Maven execution failed, exit code: '1' > at > org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase.java:89) > at > org.apache.maven.shared.release.phase.RunPerformGoalsPhase.execute(RunPerformGoalsPhase.java:67) > at > org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:336) > at > org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:282) > at > org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:262) > at > org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:129) > ... 21 more > Caused by: org.apache.maven.shared.release.exec.MavenExecutorException: > Maven execution failed, exit code: '1' > at > org.apache.maven.shared.release.exec.InvokerMavenExecutor.executeGoals(InvokerMavenExecutor.java:395) > at > org.apache.maven.shared.release.exec.InvokerMavenExecutor.executeGoals(InvokerMavenExecutor.java:413) > at > org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase.java:81) > ... 26 more > [ERROR] > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, > please read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > > > > On Thu, Oct 25, 2012 at 1:50 PM, nicolas de loof <[email protected] > > wrote: > >> so, you didn't used the ssh mode I suggested for <scm> : >> >> scm:git:[email protected]:jenkinsci/lotus-connections-plugin.git >> >> >> 2012/10/25 Phil Rumble <[email protected]> >> >>> Thank you for information >>> I made the changes, and well here is the output >>> >>> Working directory: /DD/lc/lotus-connections-plugin >>> Username for 'https://github.com': philrumble >>> Password for 'https://[email protected]': >>> [INFO] Release preparation complete. >>> [INFO] >>> [INFO] --- maven-release-plugin:2.0-beta-9:perform (default-cli) @ >>> LotusConnectionsPlugin --- >>> [INFO] Checking out the project to perform the release ... >>> [INFO] Executing: /bin/sh -c cd /DD/lc/lotus-connections-plugin/target >>> && git clone >>> git://github.com/jenkinsci/lotus-connections-plugin.git/DD/lc/lotus-connections-plugin/target/checkout >>> [INFO] Working directory: /DD/lc/lotus-connections-plugin/target >>> >>> [ERROR] The git-clone command failed. >>> [INFO] >>> ------------------------------------------------------------------------ >>> >>> [INFO] BUILD FAILURE >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] Total time: 3:42.861s >>> [INFO] Finished at: Thu Oct 25 09:23:16 WST 2012 >>> [INFO] Final Memory: 12M/33M >>> >>> [INFO] >>> ------------------------------------------------------------------------ >>> [ERROR] Failed to execute goal >>> org.apache.maven.plugins:maven-release-plugin:2.0-beta-9:perform >>> (default-cli) on project LotusConnectionsPlugin: Unable to checkout from SCM >>> [ERROR] Provider message: >>> [ERROR] The git-clone command failed. >>> [ERROR] Command output: >>> [ERROR] fatal: unable to connect to github.com: >>> [ERROR] github.com[0: 207.97.227.239]: errno=Connection refused >>> >>> [ERROR] -> [Help 1] >>> [ERROR] >>> [ERROR] To see the full stack trace of the errors, re-run Maven with the >>> -e switch. >>> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >>> [ERROR] >>> [ERROR] For more information about the errors and possible solutions, >>> please read the following articles: >>> [ERROR] [Help 1] >>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException >>> prumble@prumble-desktop:/DD/lc/lotus-connections-plugin$ >>> >>> The pom.xml has >>> >>> <scm> >>> <connection>scm:git:git:// >>> github.com/jenkinsci/lotus-connections-plugin.git</connection> >>> <developerConnection>scm:git:git:// >>> [email protected]/jenkinsci/lotus-connections-plugin.git >>> </developerConnection> >>> >>> <url>https://github.com/jenkinsci/lotus-connections-plugin</url> >>> </scm> >>> >>> >>> >>> On Wed, Oct 24, 2012 at 2:59 PM, nicolas de loof < >>> [email protected]> wrote: >>> >>>> Try using < developerConnection>scm:git:[email protected]: >>>> jenkinsci/lotus-connections-plugin.git >>>> >>>> >>>> 2012/10/24 Phil Rumble <[email protected]> >>>> >>>>> I am trying to perform a release and I get this error >>>>> >>>>> Any Ideas? >>>>> >>>>> >>>>> ------------------------------------------------------------------------ >>>>> [INFO] BUILD FAILURE >>>>> [INFO] >>>>> ------------------------------------------------------------------------ >>>>> [INFO] Total time: 3:04.045s >>>>> [INFO] Finished at: Wed Oct 24 14:48:37 WST 2012 >>>>> [INFO] Final Memory: 12M/29M >>>>> [INFO] >>>>> ------------------------------------------------------------------------ >>>>> [ERROR] Failed to execute goal >>>>> org.apache.maven.plugins:maven-release-plugin:2.0-beta-9:perform >>>>> (default-cli) on project LotusConnectionsPlugin: Unable to checkout from >>>>> SCM >>>>> [ERROR] Provider message: >>>>> [ERROR] The git-clone command failed. >>>>> [ERROR] Command output: >>>>> [ERROR] ssh: connect to host github.com port 22: Connection refused >>>>> [ERROR] fatal: The remote end hung up unexpectedly >>>>> [ERROR] -> [Help 1] >>>>> [ERROR] >>>>> [ERROR] To see the full stack trace of the errors, re-run Maven with >>>>> the -e switch. >>>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >>>>> [ERROR] >>>>> [ERROR] For more information about the errors and possible solutions, >>>>> please read the following articles: >>>>> [ERROR] [Help 1] >>>>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException >>>>> >>>>> >>>>> >>>>> On Mon, Oct 22, 2012 at 4:28 PM, nicolas de loof < >>>>> [email protected]> wrote: >>>>> >>>>>> This should be ok now >>>>>> >>>>>> >>>>>> 2012/10/22 Phil Rumble <[email protected]> >>>>>> >>>>>>> Bump... is there anyone who can help? >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Tue, Jul 17, 2012 at 9:19 PM, Phil Rumble <[email protected] >>>>>>> > wrote: >>>>>>> >>>>>>>> I don't how to do that, is there anything that I need to do? >>>>>>>> >>>>>>>> >>>>>>>> On Tue, Jul 17, 2012 at 5:07 PM, Ullrich Hafner < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> Seems that the lotus-connections-plugin is not part of >>>>>>>>> jenkins-ci. >>>>>>>>> >>>>>>>>> I don't know how to fix that with the bot (or in github)... Does >>>>>>>>> anybody know how to assign a project to jenkins-ci? >>>>>>>>> >>>>>>>>> Ulli >>>>>>>>> >>>>>>>>> >>>>>>>>> On 07/17/2012 08:40 AM, Phil Rumble wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>> I don't seem to have commit rights. Can you assist please? >>>>>>>>> >>>>>>>>> On Thu, Jul 12, 2012 at 3:00 PM, nicolas de loof < >>>>>>>>> [email protected]> wrote: >>>>>>>>> >>>>>>>>>> + CI job >>>>>>>>>> https://jenkins.ci.cloudbees.com/job/plugins/job/lotus-connections/ >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> 2012/7/12 Vojtech Juranek <[email protected]> >>>>>>>>>> >>>>>>>>>>> Hi, >>>>>>>>>>> forked as lotus-connections-plugin [1]. I got some error when >>>>>>>>>>> setting up >>>>>>>>>>> teams, so please verify that you have the commit rights. >>>>>>>>>>> Welcome aboard! >>>>>>>>>>> Vojta >>>>>>>>>>> >>>>>>>>>>> [1] https://github.com/jenkinsci/lotus-connections-plugin >>>>>>>>>>> >>>>>>>>>>> On Thursday 12 July 2012 10:32:20 Phil Rumble wrote: >>>>>>>>>>> > Done. the repo is called LotusConnectionsPlugin >>>>>>>>>>> > >>>>>>>>>>> > On Wed, Jul 11, 2012 at 1:11 PM, Vojtech Juranek < >>>>>>>>>>> [email protected]>wrote: >>>>>>>>>>> > > Hi, >>>>>>>>>>> > > could you push your plugin into github (under your account), >>>>>>>>>>> so that we >>>>>>>>>>> > > can >>>>>>>>>>> > > fork it under jenkinsci? >>>>>>>>>>> > > Thanks >>>>>>>>>>> > > Vojta >>>>>>>>>>> > > >>>>>>>>>>> > > On Tuesday 10 July 2012 22:03:43 Rumble wrote: >>>>>>>>>>> > > > Hi, >>>>>>>>>>> > > > I'd like to add a new plugin "LotusConnections" which will >>>>>>>>>>> post a build >>>>>>>>>>> > > > status message to Lotus Connections. >>>>>>>>>>> > > > My github id is 'philrumble' >>>>>>>>>>> > > > >>>>>>>>>>> > > > Thanks >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> >
