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

Configure JIRA credentials at the Job configuration level

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Won't Do
    • Icon: Major Major
    • jira-plugin
    • None

      Currently JIRA credentials can be configured only at the Jenkins Configuration level and not at the Job configuration level.

      We are providing build management support services to more than 20 divisions like Engineering, Infra, etc. This feature fills up security loop hole, When we provide Jenkins as service we don't allow teams to modify other teams jobs. In it's current form we cannot support JIRA Plugin as a service due to security issues.

          [JENKINS-32087] Configure JIRA credentials at the Job configuration level

          Valentijn Scholten added a comment - - edited

          I agree this would make the plugin more usable for bigger/enterprise environments. We don't want to people to be able to know credentials to view other departments projects/issues.
          It could be beneficials to start using the Jenkins Credentials Plugin: https://wiki.jenkins-ci.org/display/JENKINS/Credentials+Plugin

          Valentijn Scholten added a comment - - edited I agree this would make the plugin more usable for bigger/enterprise environments. We don't want to people to be able to know credentials to view other departments projects/issues. It could be beneficials to start using the Jenkins Credentials Plugin: https://wiki.jenkins-ci.org/display/JENKINS/Credentials+Plugin

          Adrien Lecharpentier added a comment -

          At this moment, the plugin is using credentials-plugin to store the username/password to connect the a Jira server. It was not the case when this ticket was created but only since 3.0.0 (May 20th, 2018).

          The thing is, from what I see, the plugin allow to configure Jira connection on the global level only. So that we can maximize the connection details usage. Having the connection details configurable on the job / folder level might go in the opposite direction (not really in the folder case but bear with me).

          I didn't see any step / action in the plugin requiring any credentials, as they all JiraSite#get to find the Jira configuration required for project.

          I'm not saying we couldn't make this happen, I'm just wondering about the need to have the Jira server connection configurable on job level, as most of the time (all the time?) the connection is configured by an administrator.

          Adrien Lecharpentier added a comment - At this moment, the plugin is using credentials-plugin to store the username/password to connect the a Jira server. It was not the case when this ticket was created but only since 3.0.0 (May 20th, 2018). The thing is, from what I see, the plugin allow to configure Jira connection on the global level only. So that we can maximize the connection details usage. Having the connection details configurable on the job / folder level might go in the opposite direction (not really in the folder case but bear with me). I didn't see any step / action in the plugin requiring any credentials, as they all JiraSite#get to find the Jira configuration required for project. I'm not saying we couldn't make this happen, I'm just wondering about the need to have the Jira server connection configurable on job level, as most of the time (all the time?) the connection is configured by an administrator.

          Mathieu Delrocq added a comment -

          Hello, we need it in our company so I will try to do it if it is ok for you. I started somes developments at https://github.com/mat1e/jira-plugin/tree/feature/JENKINS-32087_credentials_at_job_level if you want to take a look.

          Mathieu Delrocq added a comment - Hello, we need it in our company so I will try to do it if it is ok for you. I started somes developments at https://github.com/mat1e/jira-plugin/tree/feature/JENKINS-32087_credentials_at_job_level if you want to take a look.

          Radek Antoniuk added a comment -

          Since JENKINS-44524 this is configurable on the Folder level, which I think serves the purpose of security and transparency on who has access to what.
          Therefore I propose to close this and use folder configuration instead.

          Radek Antoniuk added a comment - Since JENKINS-44524 this is configurable on the Folder level, which I think serves the purpose of security and transparency on who has access to what. Therefore I propose to close this and use folder configuration instead.

          Radek Antoniuk added a comment -

          If anyone from the watchers have a usecase where a folder-level Jira configuration wouldn't be enough, please describe it here.
          If not, I will assume that when folder-level configuration is fixed, we can close this one.

          Radek Antoniuk added a comment - If anyone from the watchers have a usecase where a folder-level Jira configuration wouldn't be enough, please describe it here. If not, I will assume that when folder-level configuration is fixed, we can close this one.

          Radek Antoniuk added a comment -

          With JENKINS-61689 being almost out the door (to be released in 3.1.0) we believe that folder-level configuration is a better way to maintain configuration of credentials.
          If anyone has another use-case that would prove otherwise, feel free to open a new ticket with usage scenario description.

          Radek Antoniuk added a comment - With JENKINS-61689 being almost out the door (to be released in 3.1.0) we believe that folder-level configuration is a better way to maintain configuration of credentials. If anyone has another use-case that would prove otherwise, feel free to open a new ticket with usage scenario description.

            Unassigned Unassigned
            owood Owen Wood
            Votes:
            12 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated:
              Resolved: