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.
