All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kevin Hilman" <khilman@baylibre.com>
To: kernelci@groups.io
Subject: experiments with GCE preemptible builders
Date: Tue, 07 Apr 2020 17:34:35 -0700	[thread overview]
Message-ID: <7hpnciyfvo.fsf@baylibre.com> (raw)

Hello,

I've been trying to add more cloud builders using GCE preemptible VMs,
but am running into various Jenkins issues.

TL;DR; Jenkins Pipelines needs a lot of work to work with preemptible
builders.  :(

Long version...

First, I tried with the "JClouds plugin" which supports multiple cloud
providers.  I tried it first with GCE.  JClouds doesn't detect
preemption events at all on worker nodes, so I gave up on that rather
quickly.

Next, I tried with the "google-compute-enginge" Jenkins plugin.  It
seems to detect preemptible instances correctly.

If I create a very simple jenkins "freestyle" job (that just runs a
simple shell script), on a preemptible node, the google-compute-engine
jenkins plugin detects the builder preemption, aborts the job and
reschedules it automatically.  So that works as expected.

BUT... With pipeline jobs, things get quite a bit more complicated.

When a preemption event happens to a pipeline kernel-build job, the job
will still wait for it's timeout event (which can be a long time on
current build jobs).  When the timeout eventually happens, it detects
the preemption and the job is rescheduled.  However...

In our current jobs, if the preemption happens during the "Build" stage,
that specific build job will be rescheduled, but the build-trigger job
that called it will return SUCCESS and complete normall.

Then, the rescheduled "kernel-build" job is then rescheduled, but it's
scheduled as a non-parameterized job, so all the args we pass to jobs
are lost.

Kevin

                 reply	other threads:[~2020-04-08  0:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7hpnciyfvo.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=kernelci@groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.