"Restrict where this project can be run" job configuration option has disappeared

[dan...@gradecam.com]

Our team recently noticed that the job configuration option "Restrict where this project can be run" has disappeared. We're running the latest jenkins/jenkins:lts image (v2.107.1), in Docker. The option seems to be globally missing; I can no longer see it in any of the jobs I've looked through.

Our setup has had several slaves running with label use to constrain where jobs run for quite some time and the option was always there until recently. Despite not being visible, the jobs still seem to be constrained by the labels previously enumerated. I haven't found anything in the logs that would indicate a problem.

 Is anyone else seeing this? Any suggestions on how to isolate the problem and find a resolution? This looks like a bug, but I wanted to bounce it off the community first before creating an issue.

[Daniel Beck]

> On 29. Mar 2018, at 21:10, dan...@gradecam.com wrote:
>
> Is anyone else seeing this? Any suggestions on how to isolate the problem and find a resolution? This looks like a bug, but I wanted to bounce it off the community first before creating an issue.

Check the log for relevant looking messages (mostly startup and while loading the job config form).

Also, output of `Jenkins.instance.labels.size()` and `Jenkins.instance.clouds.size()` in the script console would be interesting.

[Daniel Petersen]

Thanks for the suggestions Daniel,

I made the mistake of assuming all jenkins output was being captured in the logs, but when you mentioned startup output, I realized it might be writing directly to the container's stdout, and sure enough, there's a ton of output there (i.e. docker logs ...). I saw an entry like this every time a job ran:

*****

WARNING: QueueListener failed while processing hudson.model.Queue$BuildableItem:hudson.model.FreeStyleProject@33998223[myJob]:576842

java.lang.NullPointerException

at com.nirima.jenkins.plugins.docker.DockerCloud.getTemplates(DockerCloud.java:445)

at com.nirima.jenkins.plugins.docker.DockerCloud.getTemplate(DockerCloud.java:397)

at com.nirima.jenkins.plugins.docker.DockerCloud.canProvision(DockerCloud.java:379)

at io.jenkins.docker.FastNodeProvisionerStrategy$FastProvisionning.onEnterBuildable(FastNodeProvisionerStrategy.java:100)

at hudson.model.Queue$BuildableItem.enter(Queue.java:2660)

at hudson.model.Queue$BuildableRunnable.run(Queue.java:2964)

at hudson.model.Queue.maintain(Queue.java:1546)

at hudson.model.Queue$1.call(Queue.java:319)

at hudson.model.Queue$1.call(Queue.java:316)

at jenkins.util.AtmostOneTaskExecutor$1.call(AtmostOneTaskExecutor.java:108)

at jenkins.util.AtmostOneTaskExecutor$1.call(AtmostOneTaskExecutor.java:98)

at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71)

at java.util.concurrent.FutureTask.run(FutureTask.java:266)

at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:112)

at java.lang.Thread.run(Thread.java:748)

Mar 30, 2018 4:27:28 PM hudson.model.Run execute

INFO: myJob #1307 main build action completed: SUCCESS

*****

Which lead me here:

https://github.com/jenkinsci/docker-plugin/issues/603

Disabling 'docker_plugin' caused the error for each job to disappear, as well as made the option "Restrict where this project can be run" to now reappear in freestyle job configs.

In case this is an issue for anyone else, the fix should be in v1.1.4.

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/R5j4-J6ln84/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6654C50B-44D8-4CF1-AF9D-301768FE8E5E%40beckweb.net.

For more options, visit https://groups.google.com/d/optout.