Hi Slide, On second read of your email I realized I'd misread what you suggested and I'd added the user/pass for server repo.jenkins-ci.org to my settings.xml. That didn't help, but once I added the user/pass for maven.jenkins-ci.orgas you'd suggested, I was away to the races. I've successfully built my second release now of the Team Concert Plugin.
http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/teamconcert/1.0.4/ Thanks so much for your help! Scott On Friday, May 3, 2013 3:39:56 PM UTC-4, Scott Cowan wrote: > > I'm not sure how I would do this from my job. I don't have access to a > .m2/settings.xml there and I don't want to put my user/password on the > command line. Maybe it's not correct to think my build should deploy to > the repo snapshots? > > > https://buildhive.cloudbees.com/job/jenkinsci/job/teamconcert-plugin/configure > > Oddly enough, this is now also failing with the same reason phrase, > "Unauthorized" when I run, > mvn -X -U -B release:prepare release:perform -Dusername=scowan > -Dpassword=<password> > locally, yet I can log in to http://repo.jenkins-ci.org with the same > credentials. > > Can anyone suggest a test I can run? Do I need to be given authorization > to upload? If so, why my the teamconcert 1.0.1 release pass? > > Thanks a bunch! > Scott > > [INFO] Uploading: > http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/teamconcert/1.0.3/teamconcert-1.0.3.hpi > [INFO] Uploading: > http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/teamconcert/1.0.3/teamconcert-1.0.3.pom > [INFO] [INFO] > ------------------------------------------------------------------------ > [INFO] [INFO] BUILD FAILURE > [INFO] [INFO] > ------------------------------------------------------------------------ > [INFO] [INFO] Total time: 6:43.468s > [INFO] [INFO] Finished at: Fri May 03 15:08:27 EDT 2013 > [INFO] [INFO] Final Memory: 66M/142M > [INFO] [INFO] > ------------------------------------------------------------------------ > [INFO] [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on > project teamconcert: Failed to deploy artifact > s: Could not transfer artifact > org.jenkins-ci.plugins:teamconcert:hpi:1.0.3 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/org/jenkins-ci/plugins/teamconcert/1.0.3/teamconcert-1.0.3.hp > i. Return code is: 401, ReasonPhrase:Unauthorized. -> [Help 1] > [INFO] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to > execute goal org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy > (default-deploy) o > n project teamconcert: Failed to deploy artifacts: Could not transfer > artifact org.jenkins-ci.plugins:teamconcert:hpi:1.0.3 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/org/jenkins-c > i/plugins/teamconcert/1.0.3/teamconcert-1.0.3.hpi. Return code is: 401, > ReasonPhrase:Unauthorized. > [INFO] at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) > [INFO] at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > [INFO] at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > [INFO] at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > [INFO] at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > [INFO] at > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > [INFO] at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > [INFO] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) > [INFO] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > [INFO] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) > [INFO] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) > [INFO] at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) > [INFO] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [INFO] at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) > [INFO] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) > [INFO] at java.lang.reflect.Method.invoke(Method.java:611) > [INFO] at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > [INFO] at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > [INFO] at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) > [INFO] at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) > [INFO] Caused by: org.apache.maven.plugin.MojoExecutionException: Failed > to deploy artifacts: Could not transfer artifact > org.jenkins-ci.plugins:teamconcert:hpi > :1.0.3 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/org/jenkins-ci/plugins/teamconcert/1.0.3/teamconcert-1.0.3.hpi. > > Return code is: 401, ReasonPhrase:Unauthorized. > [INFO] at > org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:192) > [INFO] at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) > [INFO] at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > [INFO] ... 19 more > [INFO] Caused by: > org.apache.maven.artifact.deployer.ArtifactDeploymentException: Failed to > deploy artifacts: Could not transfer artifact org.jenkins-ci.plugins > :teamconcert:hpi:1.0.3 from/to maven.jenkins-ci.org ( > http://maven.jenkins-ci.org:8081/content/repositories/releases): Failed > to transfer file: http://maven.jenk > > ins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/teamconcert/1.0.3/teamconcert-1.0.3.hpi. > > Return code is: 401, ReasonPhrase:Unauthorized. > [INFO] at > org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:141) > [INFO] at > org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:156) > [INFO] ... 21 more > [INFO] Caused by: org.sonatype.aether.deployment.DeploymentException: > Failed to deploy artifacts: Could not transfer artifact > org.jenkins-ci.plugins:teamconcert > :hpi:1.0.3 from/to maven.jenkins-ci.org ( > http://maven.jenkins-ci.org:8081/content/repositories/releases): Failed > to transfer file: http://maven.jenkins-ci.org:8 > 081/content/repositories/releases/org/jenkins-ci/plugins/teamconcert/1.0.3/teamconcert-1.0.3.hpi. > > Return code is: 401, ReasonPhrase:Unauthorized. > [INFO] at > org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:280) > [INFO] at > org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:211) > [INFO] at > org.sonatype.aether.impl.internal.DefaultRepositorySystem.deploy(DefaultRepositorySystem.java:443) > [INFO] at > org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:137) > [INFO] ... 22 more > [INFO] Caused by: org.sonatype.aether.transfer.ArtifactTransferException: > Could not transfer artifact org.jenkins-ci.plugins:teamconcert:hpi:1.0.3 > 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/org/jenkins-ci/plugins/teamconcert/1.0.3/teamconcert-1.0.3.hpi. > Return code is: 401, ReasonPhrase:Unauthorized. > [INFO] at > org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(WagonRepositoryConnector.java:951) > [INFO] at > org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(WagonRepositoryConnector.java:941) > [INFO] at > org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.run(WagonRepositoryConnector.java:837) > [INFO] at > org.sonatype.aether.connector.wagon.WagonRepositoryConnector.put(WagonRepositoryConnector.java:467) > [INFO] at > org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:274) > [INFO] ... 25 more > [INFO] Caused by: org.apache.maven.wagon.TransferFailedException: Failed > to transfer file: > http://maven.jenkins-ci.org:8081/content/repositories/releases/org/je > nkins-ci/plugins/teamconcert/1.0.3/teamconcert-1.0.3.hpi. Return code is: > 401, ReasonPhrase:Unauthorized. > [INFO] at > org.apache.maven.wagon.shared.http4.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:562) > [INFO] at > org.apache.maven.wagon.shared.http4.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:471) > [INFO] at > org.apache.maven.wagon.shared.http4.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:451) > [INFO] at > org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.run(WagonRepositoryConnector.java:811) > [INFO] ... 27 more > [INFO] [ERROR] > [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: 7:07.542s > [INFO] Finished at: Fri May 03 15:08:27 EDT 2013 > [INFO] Final Memory: 12M/35M > [INFO] > ------------------------------------------------------------------------ > > On Thursday, May 2, 2013 11:42:27 PM UTC-4, slide wrote: >> >> I was able to deploy a test version of the email-ext plugin using mvn >> clean deploy today. I had to add my Jenkins username/password to my >> settings.xml for the server with id maven.jenkins-ci.org. Here is the >> link to the test version >> >> >> http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/email-ext/2.29-SNAPSHOT/email-ext-2.29-20130503.033549-1.hpi >> >> Hopefully you get it working for you and people try out the snapshot >> version of email-ext :-) >> >> >> On Thu, May 2, 2013 at 11:11 AM, Scott Cowan <[email protected]>wrote: >> >>> Hi Mirko, >>> >>> Thanks for the suggestion. I found the snapshots repository, but >>> unfortunately when I changed my build to deploy I got a >>> TransferFailedException with reason phrase, "Unauthorized". Can I this >>> build be given authorization somehow? >>> >>> Thanks again in advance, >>> Scott >>> >>> Caused by: org.apache.maven.wagon.TransferFailedException: Failed to >>> transfer file: >>> http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/teamconcert/1.0.2-SNAPSHOT/teamconcert-1.0.2-20130502.174241-1.hpi. >>> Return code is: 401, ReasonPhrase: Unauthorized. >>> >>> >>> >>> On Thursday, May 2, 2013 4:41:15 AM UTC-4, Mirko Friedenhagen wrote: >>> >>>> Can't you just call deploy instead of install? AFAIK there is a >>>> SNAPSHOT repository at repo.jenkins-ci.org. >>>> >>>> Regards Mirko >>>> -- >>>> Sent from my mobile >>>> On May 2, 2013 5:44 AM, "Scott Cowan" <[email protected]> wrote: >>>> >>>>> Hi, >>>>> >>>>> I have the teamconcert-plugin build passing! I even successfully >>>>> released. The current job that I have is just a simple shell script type >>>>> build. I don't have any flexibility in the build steps I can perform, >>>>> unlike what I'm used to in a typical Jenkins install. You can see the >>>>> job >>>>> config here, https://buildhive.cloudbees.**com/job/jenkinsci/job/** >>>>> teamconcert-plugin/configure<https://buildhive.cloudbees.com/job/jenkinsci/job/teamconcert-plugin/configure>, >>>>> >>>>> but the shell script is just, >>>>> >>>>> cd com.ibm.team.build.hjplugin >>>>> mvn -X clean install >>>>> >>>>> I would like to be able to add a post build step to archive >>>>> com.ibm.team.build.hjplugin/**target/teamconcert.hpi so it can be >>>>> smoke tested before a release. >>>>> >>>>> 1. How do I publish a pre-release plugin for others to smoke test? >>>>> 2. Is my shell script correct, given I have two "projects" in my >>>>> github repo? >>>>> >>>>> Any help would be appreciated. Thanks, >>>>> Scott >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Jenkins Developers" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to jenkinsci-de...@**googlegroups.com. >>>>> >>>>> For more options, visit >>>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>>>> . >>>>> >>>>> >>>>> >>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Developers" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >> >> >> >> -- >> Website: http://earl-of-code.com >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
