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

Configure Global Security should accept both entries: default and per project

XMLWordPrintable

      Description

      The menu (http://myjenkins/configureSecurity) related to Authorize Project Plugin can accept both entries in the same time:

      • Project default Build Authorization
      • Per-project configurable Build Authorization

      But only Project default Build Authorization is applied to all jobs.

      Actual Behavior

      All jobs, even those with Authorization configured are run with the settings defined for Project default Build Authorization.

      Expected Behavior

      If a job has an Authorization configured explicitly in its configuration, then this one should be applied. Otherwise, the one defined in for Project default Build Authorization is applied.

      Implementation details

      This behavior can be discovered in the beginning of the build logs with:

      originally caused by:
       Started by user yyy
      Running as xxx
      

            Unassigned Unassigned
            mhochet Maxime Hochet
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: