Projects that are scheduling with SCM plugins that requires a workspace for polling, are scheduling build if the slave is offline.
That happens during jenkins startup, because jobs are loaded before computers are updated, but it also happens if the last built on slave becomes offline.
The result is a job that runs only to create a workspace for polling, and the build results in "Nothing to do"
- duplicates
-
JENKINS-8408 Large number of jobs triggered on Hudson restart
- Resolved