Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-1327

Please assist pjdarton release new vsphere-cloud plugin

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      I'm trying to produce a new release of the vsphere-cloud plugin.  This should result in version 2.16 being created.  Unfortunately I've run into problems and, after I asked in http://webchat.freenode.net/?channels=jenkins-infra , jglick suggested that I raise the issue here.

      I believe that I've followed the instructions in https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins#HostingPlugins-Releasingtojenkins-ci.org by setting up ~/.m2/settings.xml with my Artifactory username and password, and merged in the settings.xml file from https://wiki.jenkins.io/display/JENKINS/Plugin+tutorial#Plugintutorial-SettingUpEnvironment

      I'm using ssh keys to log into github (same username, "pjdarton").

      This has resulted in me being able to "git clone git@github.com:jenkinsci/vsphere-cloud-plugin.git", and I can "mvn deploy" to create a snapshot, but if I do "mvn release:prepare release:perform" then I get the error:

          [INFO] — maven-deploy-plugin:2.8.2:deploy (default-deploy) @ vsphere-cloud —
          Uploading: https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/vsphere-cloud/2.16/vsphere-cloud-2.16.hpi
          Uploading: https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/vsphere-cloud/2.16/vsphere-cloud-2.16.pom
          [INFO] ------------------------------------------------------------------------
          [INFO] BUILD FAILURE
          [INFO] ------------------------------------------------------------------------
          [INFO] Total time: 2:49.329s
          [INFO] Finished at: Wed Sep 06 16:01:27 BST 2017
          [INFO] Final Memory: 63M/338M
          [INFO] ------------------------------------------------------------------------
          [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project vsphere-cloud: Failed to deploy artifacts: Could not transfer artifact org.jenkins-ci.plugins:vsphere-cloud:hpi:2.16 from/to maven.jenkins-ci.org (https://repo.jenkins-ci.org/releases/): Access denied to: https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/vsphere-cloud/2.16/vsphere-cloud-2.16.hpi, ReasonPhrase: Forbidden. -> [Help 1]

       

      The previous plugin maintainer (Jason Swager) raised https://github.com/jenkins-infra/repository-permissions-updater/pull/376 to get me added to the permissions for this plugin and, while I do now have access to GitHub, it doesn't appear to have taken effect on Artifactory.

      My guess is that daniel-beck's comment https://github.com/jenkins-infra/repository-permissions-updater/pull/376#issuecomment-321300373 may well identify the root cause here ... but as Eric (elordahl) did not respond to prompts this has left me unable to proceed ...

      ... is it possible to kick things manually?

        Attachments

          Activity

          Hide
          danielbeck Daniel Beck added a comment -

          File a PR to remove the user blocking the permissions from getting applied, referencing that comment and this issue.

          Show
          danielbeck Daniel Beck added a comment - File a PR to remove the user blocking the permissions from getting applied, referencing that comment and this issue.
          Show
          pjdarton pjdarton added a comment - PR filed.  https://github.com/jenkins-infra/repository-permissions-updater/pull/423  
          Hide
          pjdarton pjdarton added a comment -

          Question:  Once the Artifactory permissions issues are resolved, should I remove the two commits made by the maven-release-plugin ( https://github.com/jenkinsci/vsphere-cloud-plugin/commit/f4d4e057f52c44386ce06eead47fe4476113a54b and https://github.com/jenkinsci/vsphere-cloud-plugin/commit/3227db95d5b47c9a34f3755b535f7592430787a7 ), and any tags etc, before trying to do the release again?

          ...or does the maven-release-plugin code cope with there being tags there already and simply skip to the "upload to artifactory" stage?

          Show
          pjdarton pjdarton added a comment - Question:  Once the Artifactory permissions issues are resolved, should I remove the two commits made by the maven-release-plugin (  https://github.com/jenkinsci/vsphere-cloud-plugin/commit/f4d4e057f52c44386ce06eead47fe4476113a54b and https://github.com/jenkinsci/vsphere-cloud-plugin/commit/3227db95d5b47c9a34f3755b535f7592430787a7 ), and any tags etc, before trying to do the release again? ...or does the maven-release-plugin code cope with there being tags there already and simply skip to the "upload to artifactory" stage?
          Hide
          pjdarton pjdarton added a comment -

          All done - vSphere plugin 2.16 has released.

          I've even updated the wiki page with release notes

          Thanks for your assistance.

          Show
          pjdarton pjdarton added a comment - All done - vSphere plugin 2.16 has released. I've even updated the wiki page with release notes Thanks for your assistance.

            People

            • Assignee:
              danielbeck Daniel Beck
              Reporter:
              pjdarton pjdarton
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: