From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] Add gitlab-CI support
Date: Sun, 5 Mar 2017 22:25:16 +0100 [thread overview]
Message-ID: <20170305222516.78689464@free-electrons.com> (raw)
In-Reply-To: <20170213232303.7053-1-arnout@mind.be>
Hello,
On Tue, 14 Feb 2017 00:23:03 +0100, Arnout Vandecappelle
(Essensium/Mind) wrote:
> The buildroot repository is now mirrored on
> https://gitlab.com/buildroot.org/buildroot so we can use Gitlab-CI to
> test Buildroot. Gitlab-CI is controlled by a .gitlab-ci.yml file
> that exists in the repository.
I've applied with some minor changes (see below).
> Building all the defconfigs takes a long time. Gitlab-CI will do that
> every time it pulls from git.buildroot.org, which is once per hour.
> That is way too often. Therefore, the defconfigs are not built on pull,
> but only on explicit trigger through the API or when a tag is added.
What is the next step now? Who is going to run in a cronjob the thing
that triggers the build? Can we setup a notification on the mailing
list and/or IRC when there is a failure?
> + # The container has not package lists, so need to update first
I've fixed the typo not -> no, as noticed by Marcus.
> +.gitlab-ci.yml: .gitlab-ci.yml.in configs/*_defconfig
> + (cd configs; ls -1 *_defconfig) | sed 's/$$/: *defconfig/' | cat $< - > $@
I've added LC_ALL=C when calling ls -1, because I did not had the same
order as yours when regenerating the list of defconfigs. Apparently,
depending on the locales armadeus is before or after arm_.
And I've regenerated the list of defconfigs before pushing, of course.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-05 21:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 23:23 [Buildroot] [PATCH v3] Add gitlab-CI support Arnout Vandecappelle
2017-02-13 23:53 ` Marcus Hoffmann
2017-02-15 23:17 ` Arnout Vandecappelle
2017-03-05 21:25 ` Thomas Petazzoni [this message]
2017-03-05 22:17 ` Arnout Vandecappelle
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=20170305222516.78689464@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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 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.