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

Triggering a build from the context menu produces a warning when security is enabled

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • Jenkins 1.480.3 (Winstone and Tomcat)
      LDAP plugin 1.1 and 1.2

      Hovering mouse over a job name brings up a context menu. Clicking Build Now from the context menu produces the following warning and a Proceed button. Build starts only if Proceed button is pressed. Context menu is accessible at least in job list view (e.g. default All view) and from the breadcrumb. Clicking Build Now on the left menu on a job page works normally, i.e. without warnings.

      You must use POST method to trigger builds. (From scripts you may instead pass a per-project authentication token, or authenticate with your API token.) If you see this page, it may be because a plugin offered a GET link; file a bug report for that plugin.

          [JENKINS-16844] Triggering a build from the context menu produces a warning when security is enabled

          Sami Salonen created issue -
          Sami Salonen made changes -
          Component/s New: ldap [ 17122 ]
          Component/s Original: core [ 15593 ]
          Sami Salonen made changes -
          Environment Original: Jenkins 1.480.3 (Winstone and Tomcat) New: Jenkins 1.480.3 (Winstone and Tomcat)
          LDAP plugin 1.1 and 1.2
          Sami Salonen made changes -
          Component/s New: core [ 15593 ]
          Component/s New: security [ 15508 ]
          Description Original: Hovering mouse over a job name brings up a context menu. Clicking Build Now from the context menu produces the following warning and a Proceed button. Build starts only if Proceed button is pressed. Context menu is accessible at least in job list view (e.g. default All view) and from the breadcrumb. Clicking Build Now on the left menu on a job page works normally.

          {{You must use POST method to trigger builds. (From scripts you may instead pass a per-project authentication token, or authenticate with your API token.) If you see this page, it may be because a plugin offered a GET link; file a bug report for that plugin.}}
          New: Hovering mouse over a job name brings up a context menu. Clicking _Build Now_ from the context menu produces the following warning and a _Proceed_ button. Build starts only if _Proceed_ button is pressed. Context menu is accessible at least in job list view (e.g. default _All_ view) and from the breadcrumb. Clicking _Build Now_ on the left menu on a job page works normally, i.e. without warnings.

          {{You must use POST method to trigger builds. (From scripts you may instead pass a per-project authentication token, or authenticate with your API token.) If you see this page, it may be because a plugin offered a GET link; file a bug report for that plugin.}}
          Summary Original: Triggering a build from the context menu produces a warning New: Triggering a build from the context menu produces a warning when security is enabled
          Sami Salonen made changes -
          Component/s New: gui [ 15492 ]
          Jesse Glick made changes -
          Assignee New: Jesse Glick [ jglick ]
          Jesse Glick made changes -
          Link New: This issue is blocking SECURITY-13 [ SECURITY-13 ]
          Jesse Glick made changes -
          Component/s Original: gui [ 15492 ]
          Component/s Original: security [ 15508 ]
          Component/s Original: ldap [ 17122 ]
          Jesse Glick made changes -
          Link New: This issue is duplicated by JENKINS-16913 [ JENKINS-16913 ]
          Ryan Campbell made changes -
          Attachment New: allow-local-build.patch [ 23212 ]
          Jesse Glick made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

            jglick Jesse Glick
            salsa Sami Salonen
            Votes:
            2 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: