Hmm, quite strange, I've just run 'deploy' target from 'lifecycle' in Idea and plugin was successfully released. Will it appear here <https://github.com/jenkinsci/build-name-setter-plugin/releases>?
On Tuesday, November 3, 2015 at 11:18:43 PM UTC+3, Lev Mishin wrote: > > Hi again > I have read all the article but I unable to deploy a new version. I try to > run mvn release:prepare release:perform -Dusername=... -Dpassword=... with > login/pass, but the error occurs: > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on > project build-name-setter: Failed to deploy artifacts: Could not transfer > artifact org.jenkins-ci.plugins:build-name-setter:hpi:1.5 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/build-name-setter/1.5/build-name-setter-1.5.hpi. > > Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1] > > I guess it is connected with: > However if your plugin is hosted on GitHub and you have different username > and/or password for GitHub and jenkins-ci.org use of the command-line > arguments for username/password will result in errors. > > Am I right? > I have set up ssh-agent using the following instructions: > Generate key <https://help.github.com/articles/generating-ssh-keys/> > Setup ssh agent > <https://developer.github.com/guides/using-ssh-agent-forwarding/#setting-up-ssh-agent-forwarding> > But maven still fails with the error above > > > > On Friday, October 9, 2015 at 7:24:55 PM UTC+3, Lev Mishin wrote: >> >> >> - Github link: >> >> https://github.com/Le0Michine/Jenkins-Build-name-updater-plugin/tree/master >> >> - Repo name: "Build-name-updater-plugin" >> - User name the same as in the URL >> - jenkins-ci.org username: Le0; >> - Description: my plugin updates a build name during the build >> process, it was necessary because custom build name could tell some >> useful >> information. Sometimes we just unable to set custom build name before >> build >> or in pre-build steps because we just don't know that so using my plugin >> you can set the build name in a separate build step, you can use a file >> in >> the build workspace or environment variable or both of them as the build >> name source. >> >> -- >> >> Kind regards, >> Lev Mishin >> > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/d225bdee-6216-41a2-9198-205b0992db43%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
