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

Builds are not processed when triggered manually

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Minor Minor
    • kubernetes-plugin
    • Google Kubernetes Engine Cluster
      Kubernetes Version 1.12.8-gke.10
      Jenkins Version 2.176.3
      kubernetes-plugin Version 1.19.0

      When builds are triggeres manually by the "Build Now" button, then an agent will be created, but the builds are not processed. I just get:

      Started by user myuser
      Running as myuser
      Obtained Jenkinsfile from 95690226dba08354f99f1ef4adb30cf01fddee6d
      Running in Durability level: MAX_SURVIVABILITY
      [Pipeline] Start of Pipeline
      [Pipeline] readTrusted
      Obtained build/jenkins/pod.yaml from 95690226dba08354f99f1ef4adb30cf01fddee6d
      [Pipeline] podTemplate
      [Pipeline] {
      [Pipeline] node
      Still waiting to schedule task
      ‘dr.how-jenkins-image-develop-7-90t6s-plm5r-kt00q’ is offline

      If the build was triggered by a webhook, everything works as expected.

      The kubernetes plugin is configured as followed:

          [JENKINS-59313] Builds are not processed when triggered manually

          Stefan Mayer added a comment -

          Misconfiguration of authorize project plugin was the problem

          Stefan Mayer added a comment - Misconfiguration of authorize project plugin was the problem

          Jon Denly added a comment - - edited

          hex_sm Any chance you can provide more information on the fix? We have the same problem and are using the authorize project plugin.

          EDIT: The fix for us was to add the Agent/Build permission globally for authenticated users, having it at folder level was not enough.

          Jon Denly added a comment - - edited hex_sm Any chance you can provide more information on the fix? We have the same problem and are using the authorize project plugin. EDIT: The fix for us was to add the Agent/Build permission globally for authenticated users, having it at folder level was not enough.

            hex_sm Stefan Mayer
            hex_sm Stefan Mayer
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: