"mvn deploy" failed at first and you were right - credentials seemed to be expired and I had to update it. After update "mvn deploy" from clean folder succeeded however when I tried doing 'mvn release:prepare release:perform' from my original folder I got
[INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 5.464 s [INFO] Finished at: 2021-11-19T16:32:57-05:00 [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5.1:prepare (default-cli) on project klocwork: Unable to tag SCM [ERROR] Provider message: [ERROR] The git-tag command failed. [ERROR] Command output: [ERROR] fatal: tag 'klocwork-2021.3' already exists I imagine this is because initial release pushed something to github and possibly to release repository.. Is there a way to fix it you assume and have it released under 2021.3 version? Or the only way now is to release it with another version? From: [email protected] <[email protected]> On Behalf Of Mark Waite Sent: Friday, November 19, 2021 2:00 PM To: Jenkins Developers <[email protected]> Subject: Re: release went wrong? On Friday, November 19, 2021 at 11:28:09 AM UTC-7 Sergei Butylin wrote: I got the message while doing "mvn release:prepare release:perform" We've been following the same steps here https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.jenkins.io%2Fdisplay%2FJENKINS%2FHosting%2BPlugins&data=04%7C01%7Csbutylin%40perforce.com%7C08d6cbf5a9af4efe193008d9ab8ebc46%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C637729453604249100%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=N8hVIHtBRyoEOvWbsPBmO%2BL21VlcjO6y6nr7jRlr47g%3D&reserved=0> and here https://www.jenkins.io/doc/developer/publishing/releasing-manually/<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fpublishing%2Freleasing-manually%2F&data=04%7C01%7Csbutylin%40perforce.com%7C08d6cbf5a9af4efe193008d9ab8ebc46%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C637729453604259096%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=X4mGDI4q4somPWr1Iun9lp5ixAhQJ0O3ffNPF0z%2FP1o%3D&reserved=0> and previous releases went well. Question is how can we rollback the failed release that you can see in github history here https://github.com/jenkinsci/klocwork-plugin/commits/master and try do 2021.3 the release again? I've not had great results personally with attempting to redo a maven release. However, if you've retained the directory where you performed the original `mvn release:prepare release:perform` you could try running `mvn release:perform` another time. Before attempting `mvn release:perform`, you should confirm that you have permission to push your release to https://repos.jenkins-ci.org/ . I believe that one way to do that would be with the following commands to deploy a snapshot of your plugin from another working directory (don't do this from the directory where you attempted the previous mvn release:prepare release:perform): $ cd /tmp $ git clone https://github.com/jenkinsci/klocwork-plugin/ $ cd klocwork-plugin $ mvn deploy If that succeeds, you will have deployed a snapshot version of the default branch to the snapshots section of repos.jenkins-ci.org If that fails, you probably need to reset your password at https://accounts.jenkins.io or at https://beta.accounts.jenkins.io Mark Waite -- 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]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e767789e-4596-4c99-a779-cfb0140cbdd1n%40googlegroups.com<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Fmsgid%2Fjenkinsci-dev%2Fe767789e-4596-4c99-a779-cfb0140cbdd1n%2540googlegroups.com%3Futm_medium%3Demail%26utm_source%3Dfooter&data=04%7C01%7Csbutylin%40perforce.com%7C08d6cbf5a9af4efe193008d9ab8ebc46%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C637729453604259096%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=x68Cz1LfP9f6vJz2NuIIm9qG%2FgM2ykNtW9HSuCYf%2Fss%3D&reserved=0>. CAUTION: This email originated from outside of the organization. Do not click on links or open attachments unless you recognize the sender and know the content is safe. This e-mail may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately. -- 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/DM6PR20MB26665414E9535F5C74076CA9AD9C9%40DM6PR20MB2666.namprd20.prod.outlook.com.
