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

Allow configuration job / folder based instead of global based

      I want to start using the cloud manager plugin to connect from our own private CI / CD to the Adobe Cloud Manager. As an Adobe partner we have multiple clients that use Jenkins for this, but for none of them we have Admin role. All jobs / configurations should always be set up on job / folder level, where we have permissions to manage a specific folder / view. 

      This does not seem to be possible with the cloud manager plugin, where having admin rights seems to be a necessity to configure the adobe io connection. I would like to ask to see if this can be improved to have the domain credentials on a lower level than System, which is not feasible in big corporations where Jenkins is used for multiple teams

          [JENKINS-67531] Allow configuration job / folder based instead of global based

          Roy Teeuwen created issue -
          Roy Teeuwen made changes -
          Summary Original: Allow configuration folder based instead of global based New: Allow configuration job / folder based instead of global based
          Roy Teeuwen made changes -
          Description Original: I want to start using the cloud manager plugin to connect from our own private CI / CD to the Adobe Cloud Manager. As an Adobe partner we have multiple clients that use Jenkins for this, but for none of them we have Admin role. All jobs / configurations should always be set up on folder level, where we have permissions to manage a specific folder / view. 

          This does not seem to be possible with the cloud manager plugin, where having admin rights seems to be a necessity to configure the adobe io connection. I would like to ask to see if this can be improved to have the domain credentials on a lower level than System, which is not feasible in big corporations where Jenkins is used for multiple teams
          New: I want to start using the cloud manager plugin to connect from our own private CI / CD to the Adobe Cloud Manager. As an Adobe partner we have multiple clients that use Jenkins for this, but for none of them we have Admin role. All jobs / configurations should always be set up on job / folder level, where we have permissions to manage a specific folder / view. 

          This does not seem to be possible with the cloud manager plugin, where having admin rights seems to be a necessity to configure the adobe io connection. I would like to ask to see if this can be improved to have the domain credentials on a lower level than System, which is not feasible in big corporations where Jenkins is used for multiple teams
          Bryan Stopp made changes -
          Assignee Original: Ahmed Musallam [ ahmedmusallam ] New: Bryan Stopp [ stopp ]

            stopp Bryan Stopp
            royteeuwen Roy Teeuwen
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: