Jenkins jobs aren't starting

Things to consider

1. How long has it been since you triggered the job?
   1. Nodes are spun up on demand and can sometimes take >10 minutes to get fully provisioned and connected to the Jenkins server
2. How big is the build queue?
   1. Contention for build labels and VM resources can be a limiting factor (<amount of CPUs/ RAM/ etc from cloud provider)
3. If the previous two things are past reasonable expectation, please open a ticket and the Release Engineering team will take a look.

Related articles

• Page:
  [CI] Connect 3rd party CI
• Page:
  [CI - Packer] Add software to CI builders
• Page:
  Jenkins jobs aren't starting