public inbox for kernelci@lists.linux.dev
 help / color / mirror / Atom feed
From: "Kevin Hilman" <khilman@baylibre.com>
To: kernelci@groups.io, guillaume.tucker@gmail.com, kernelci@groups.io
Cc: Linus Walleij <linus.walleij@linaro.org>
Subject: Re: Hourly, daily, weekly monitoring
Date: Mon, 04 Mar 2019 17:53:11 -0800	[thread overview]
Message-ID: <7hlg1ujddk.fsf@baylibre.com> (raw)
In-Reply-To: <1eb2fcf9-d08b-0d38-9aee-c0206089b5d7@collabora.com>

"Guillaume Tucker" <guillaume.tucker@gmail.com> writes:

> Hello,
>
> All the branches currently build on kernelci.org are monitored
> for new changes every hour.  While this has shown over time to be
> a good frequency for mainline branches, some subsystem ones may
> be updated a lot more often.  Monitoring them every hour would
> cause a lot of unnecessary builds and tests.  This topic was
> recently brought up again[1] around the addition of the GPIO
> branches, which Linus Walleij said could be monitored once a day
> instead.
>
> So it seems like it would be beneficial to add some parameters to
> the YAML build configuration to be able to tell how often each
> branch needs to be checked for new commits.  There should also be
> some command line option in kci_build to help implementing that
> in an automated build system such as Jenkins Pipeline (say, to
> know the time when a branch needs to be checked again...).
>
> I'm not entirely sure how much flexibility Jenkins can offer in
> that respect, but at least having 3 versions of the monitor job
> that runs every hour, every day and every week should cover all
> the cases.  If possible, we may be able to implement something
> that dynamically schedules the next check for each branch.
>
> How does that sound?

Sounds great.  This is something we've been needing for awhile.

Kevin

  reply	other threads:[~2019-03-05  1:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-04 13:20 Hourly, daily, weekly monitoring Guillaume Tucker
2019-03-05  1:53 ` Kevin Hilman [this message]
2019-03-05 12:14 ` Mark Brown
2019-03-05 22:04   ` Dan Rue
2019-03-06  9:16     ` Guillaume Tucker
2019-03-06 17:00       ` Mark Brown

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=7hlg1ujddk.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=guillaume.tucker@gmail.com \
    --cc=kernelci@groups.io \
    --cc=linus.walleij@linaro.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox