Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-71018

spotinst plugin: giving release permissions to user

    • Icon: Task Task
    • Resolution: Not A Defect
    • Icon: Minor Minor
    • spotinst-plugin
    • None
    • spotinst

      Give permissions to user: Zivmessing as member
      needs permissions to merge and release new plugin versions

          [JENKINS-71018] spotinst plugin: giving release permissions to user

          Mark Waite added a comment -

          spotinst thanks for the request.

          You need to submit a pull request to update the repository permissions updater by adding a new uploader to the spotinst.yml file. Be sure that you use the accounts.jenkins.io username of that user and be sure that they have logged into Artifactory with their accounts.jenkins.io username.

          I've closed this issue because the issue tracker won't help you with this request. A pull request to the repository permissions updater is what you need.

          Mark Waite added a comment - spotinst thanks for the request. You need to submit a pull request to update the repository permissions updater by adding a new uploader to the spotinst.yml file . Be sure that you use the accounts.jenkins.io username of that user and be sure that they have logged into Artifactory with their accounts.jenkins.io username. I've closed this issue because the issue tracker won't help you with this request. A pull request to the repository permissions updater is what you need.

          Spotinst team added a comment -

          Hey markewaite, thanks for the quick response.

          I would like that Zivmessing will have the same permissions as adivos, however, I don't see adivos listed in the spotinst.yml file.

          To clarify, adivos has permissions to release versions of our plugin.

          Can you please explain how could that be happening?

          Also, attached 2 previous requests to give Zivmessing the permissions mentioned:
          https://github.com/jenkins-infra/helpdesk/issues/2638
          https://github.com/jenkins-infra/helpdesk/issues/2743

          Both of the requests marked as resolved, but were never solved.

          Thank you

          Spotinst team added a comment - Hey markewaite , thanks for the quick response. I would like that Zivmessing  will have the same permissions as adivos , however, I don't see adivos listed in the  spotinst.yml file . To clarify, adivos has permissions to release versions of our plugin. Can you please explain how could that be happening? Also, attached 2 previous requests to give Zivmessing the permissions mentioned: https://github.com/jenkins-infra/helpdesk/issues/2638 https://github.com/jenkins-infra/helpdesk/issues/2743 Both of the requests marked as resolved, but were never solved. Thank you

          Mark Waite added a comment -

          You wrote:

          I would like that Zivmessing will have the same permissions as adivos, however, I don't see adivos listed in the spotinst.yml file.

          To clarify, adivos has permissions to release versions of our plugin.

          Can you please explain how could that be happening?

          Possibly adivos had permissions previously and those permissions were not removed?

          Also, attached 2 previous requests to give Zivmessing the permissions mentioned:
          https://github.com/jenkins-infra/helpdesk/issues/2638
          https://github.com/jenkins-infra/helpdesk/issues/2743

          Both of the requests marked as resolved, but were never solved.

          The Jenkins infrastructure team generally does not submit permission update pull requests on behalf of others. Their most typical action on that type of help desk ticket is to tell you where to submit the pull request yourself. Permission update pull requests need to be accompanied by the requested user logging into the artifact repository with their username from accounts.jenkins.io. The infrastructure team can't do that login for someone else.

          As I said earlier:

          You need to submit a pull request to update the repository permissions updater by adding a new uploader to the spotinst.yml file. Be sure that you use the accounts.jenkins.io username of that user and be sure that they have logged into Artifactory with their accounts.jenkins.io username.

          Mark Waite added a comment - You wrote: I would like that Zivmessing will have the same permissions as adivos, however, I don't see adivos listed in the spotinst.yml file. To clarify, adivos has permissions to release versions of our plugin. Can you please explain how could that be happening? Possibly adivos had permissions previously and those permissions were not removed? Also, attached 2 previous requests to give Zivmessing the permissions mentioned: https://github.com/jenkins-infra/helpdesk/issues/2638 https://github.com/jenkins-infra/helpdesk/issues/2743 Both of the requests marked as resolved, but were never solved. The Jenkins infrastructure team generally does not submit permission update pull requests on behalf of others. Their most typical action on that type of help desk ticket is to tell you where to submit the pull request yourself. Permission update pull requests need to be accompanied by the requested user logging into the artifact repository with their username from accounts.jenkins.io. The infrastructure team can't do that login for someone else. As I said earlier: You need to submit a pull request to update the repository permissions updater by adding a new uploader to the spotinst.yml file . Be sure that you use the accounts.jenkins.io username of that user and be sure that they have logged into Artifactory with their accounts.jenkins.io username.

            aharont Aharon Twizer
            spotinst Spotinst team
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: