21 hours of failed builds after initial pipeline setup: "Aborting release because the Jenkins VM requires initialization."

[GoogleCodeExporter]

What steps will reproduce the problem?
This appears to occur during the initial setup of a Release Pipeline. The first 
and subsequent builds generate a succession of 4 failed builds over a 21 hour 
period. All of them with the same error:

"Aborting release because the Jenkins VM requires initialization. Please wait a 
few minutes and try again."

See this forum entry discussing the issue:
https://groups.google.com/forum/#!msg/google-cloud-sdk/cr5TpwQDQ78/yc3fL-i6Sk8J

What is the expected output? What do you see instead?
Expected to see the build start.

What is the output of 'gcloud info'?
This shouldn't be relevant:

Google Cloud SDK [0.9.37]
Platform: [Mac OS X, x86_64]
Python Version: [2.7.6 (default, Sep  9 2014, 15:04:36)  [GCC 4.2.1 Compatible 
Apple LLVM 6.0 (clang-600.0.39)]]
Site Packages: [Disabled]

Please provide any additional information below.

Project ID: 364775480802

Build Times:
Nov 19, 2014, 11:25:30 AM
Nov 18, 2014, 4:18:35 PM
Nov 18, 2014, 2:57:45 PM
Nov 18, 2014, 2:42:55 PM

Original issue reported on code.google.com by bru...@gmail.com on 30 Nov 2014 at 1:38

[GoogleCodeExporter]

Thank for reporting the issue. We will get someone from the release pipelines 
team to look into this.

Original comment by vil...@google.com on 1 Dec 2014 at 3:36

• Changed state: Accepted

[GoogleCodeExporter]

I should add that after this period, the build started working without any 
changes on my part except for triggering a new build with a GitHub commit.

Original comment by bru...@gmail.com on 1 Dec 2014 at 9:52

[GoogleCodeExporter]

Original comment by jeffvaug...@google.com on 20 Jan 2015 at 8:25

• Changed state: Obsolete