-
Bug
-
Resolution: Fixed
-
Minor
-
Jenkins 2.286 freshly upgraded from Jenkins 2.285
Test 2.285 instance has been upgraded to 2.286 (switching jenkins/jenkins:2.285-centos to jenkins/jenkins:2.286-centos container)
There is one permanent agent (apart from "master") and Kubernetes cloud configured. We never build on master node and we use declarative pipelines exclusively.
After 2.285 -> 2.286 upgrade I was greeted with the following admin warning:
You should set up distributed builds. Building on the controller node can be a security issue. See the documentation.
"Manage" button takes be to the master node configuration but it is not clear what to do there.
Test | Result |
---|---|
!Main.isDevelopmentMode | true |
Jenkins.get().getNumExecutors() | 1 |
Jenkins.get().clouds.isEmpty() | false |
Jenkins.get().getNodes().isEmpty() | false |
- links to
So, I have figured it out that the issue was the number of executors on the master node was 1.
I have done the following:
The linked doc says, among others, you should generally configure the master to have no executor
Can we make this clear in the message? It was confusing because I thought *I have* configured distributed builds; I have not disabled the master completely. (This is not obvious, either, I was poking around looking for "Disable" or "Delete" button on "master", no luck).