Signed-off-by: California Sullivan
---
README-GOOGLE-CLOUD | 46 ++
1 file changed, 30 insertions(+), 16 deletions(-)
diff --git a/README-GOOGLE-CLOUD b/README-GOOGLE-CLOUD
index 30bf5b6..34c80a9 100644
--- a/README-GOOGLE-CLOUD
+++ b/README-GOOGLE
It can delete multiple at once if multiple were created at once.
Signed-off-by: California Sullivan
---
.../autobuilder/buildsteps/DeleteGoogleVM.py | 52 --
.../autobuilder/buildsteps/DeleteGoogleVMs.py | 52 ++
2 files changed, 52 insertions
In the case that somebody turned off a build before it completed, the
buildstep would attempt and fail to procure a new VM, failing the build.
Signed-off-by: California Sullivan
---
.../autobuilder/buildsteps/ProvisionGoogleVMs.py | 16 ++--
1 file changed, 10 insertions
See https://bugzilla.yoctoproject.org/show_bug.cgi?id=5975
On Tue, Sep 23, 2014 at 10:13 AM, wrote:
> From: California Sullivan
>
> This build step provisions a Google VM using the gcloud command line tool.
>
> Signed-off-by: California Sullivan
> ---
> .../a
Signed-off-by: California Sullivan
On Mon, Sep 22, 2014 at 3:23 PM, Elizabeth Flanagan <
elizabeth.flana...@intel.com> wrote:
> The first pass of the yocto-autobuilder developer document is available at:
>
>
> http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/log
.
---
Cal
On Tue, Sep 2, 2014 at 1:45 PM, Flanagan, Elizabeth <
elizabeth.flana...@intel.com> wrote:
> On Thu, Aug 28, 2014 at 4:33 PM, California Sullivan
> wrote:
> > When a build was configured to use the TriggerBuilds build step, it would
> > take on the buildsla
When a build was configured to use the TriggerBuilds build step, it would
take on the buildslave of the last triggered build rather than its own.
Signed-off-by: California Sullivan
---
lib/python2.7/site-packages/autobuilder/Autobuilder.py | 3 +--
1 file changed, 1 insertion(+), 2 deletions
