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

Issue Type:	Bug
Assignee:	Unassigned
Components:	kubernetes-plugin
Created:	2019-09-11 08:47
Environment:	Google Kubernetes Engine Cluster Kubernetes Version 1.12.8-gke.10 Jenkins Version 2.176.3 kubernetes-plugin Version 1.18.3
Labels:	kubernetes-plugin agents kubernetes
Priority:	Minor
Reporter:	Stefan Mayer

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:

Name: Kubernetes
Kubernetes URL: https://kubernetes.default.svc.cluster.local
Jenkins URL: http://jenkins.jenkins.svc.cluster.local:8080
Jenkins: Tunnel: jenkins.jenkins.svc.cluster.local:50000
Pod Retention: Never
Max connections to Kubernetes API: 0
Seconds to wait for pod to be running: 600

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

Stefan.Mayer@Handbuch-Experten.de (JIRA)

unread,

Sep 11, 2019, 4:50:02 AM9/11/19

to jenkinsc...@googlegroups.com

Stefan Mayer updated an issue

Jenkins /

Change By:	Stefan Mayer
Environment:

Google Kubernetes Engine Cluster
Kubernetes Version 1.12.8-gke.10
Jenkins Version 2.176.3

kubernetes-plugin Version 1. 18 19 . 3 0

Stefan.Mayer@Handbuch-Experten.de (JIRA)

unread,

Sep 11, 2019, 5:07:02 AM9/11/19

to jenkinsc...@googlegroups.com

Stefan Mayer assigned an issue to Stefan Mayer

Jenkins /

Change By:	Stefan Mayer
Assignee:	Stefan Mayer

Stefan.Mayer@Handbuch-Experten.de (JIRA)

unread,

Sep 11, 2019, 5:08:03 AM9/11/19

to jenkinsc...@googlegroups.com

Stefan Mayer closed an issue as Won't Fix

Misconfiguration of authorize project plugin was the problem

Jenkins /

Change By:	Stefan Mayer
Status:	Open Closed
Resolution:	Won't Fix

jonnydee@gmail.com (JIRA)

unread,

Dec 9, 2019, 11:58:02 PM12/9/19

to jenkinsc...@googlegroups.com

Jon Denly commented on

Re: Builds are not processed when triggered manually

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

jonnydee@gmail.com (JIRA)

unread,

Dec 17, 2019, 6:30:02 PM12/17/19

to jenkinsc...@googlegroups.com

Jon Denly edited a comment on

Re: Builds are not processed when triggered manually

[~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.