From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Availability of old build results
Date: Fri, 06 Dec 2013 17:10:35 +0100 [thread overview]
Message-ID: <52A1F6FB.1070101@mind.be> (raw)
In-Reply-To: <CAAXf6LWmaYb0cohOcbt5CdkXjMmeOFOLgbWN5eKQBqd66MCX5w@mail.gmail.com>
On 06/12/13 10:57, Thomas De Schampheleire wrote:
> If the patch is fixing an autobuild problem, we really should be
> repeating that autobuild configuration instead (but that could be done
> manually by someone).
I think it would be nice if a failing autobuild configuration would
automatically be added to jenkins, and that it would be automatically
removed from there once it succeeds. Of course, that is only feasible if
the number of failures is low (maximum 1 or 2 per day) and they get fixed
quickly, otherwise jenkins will blow up. So it's not something we can
consider right away.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2013-12-06 16:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 23:25 [Buildroot] Availability of old build results Thomas Petazzoni
2013-12-05 23:41 ` Yann E. MORIN
2013-12-06 7:36 ` Thomas De Schampheleire
2013-12-06 8:47 ` Peter Korsgaard
2013-12-06 8:50 ` Thomas Petazzoni
2013-12-06 9:57 ` Thomas De Schampheleire
2013-12-06 10:11 ` Thomas Petazzoni
2013-12-07 20:43 ` Thomas De Schampheleire
2013-12-06 16:10 ` Arnout Vandecappelle [this message]
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=52A1F6FB.1070101@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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