From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] .travis.yml: rework according to new travis-ci infra
Date: Wed, 3 Feb 2016 09:58:20 -0700 [thread overview]
Message-ID: <56B231AC.9040807@wwwdotorg.org> (raw)
In-Reply-To: <20160202015724.GJ25786@bill-the-cat>
On 02/01/2016 06:57 PM, Tom Rini wrote:
> On Mon, Jan 25, 2016 at 08:22:41PM +0100, Roger Meier wrote:
>
>> - install using addons.apt
>> - remove MAKEALL
>> - split mpc85xx boards
>> - remove TEST_CONFIG_CMD, just info
>> - fetch mips toolchain via buildman
>> - remove --list-error-boards param
>> - conditional script
>> - use TOOLCHAIN instead of INSTALL_TOOLCHAIN
>> - add aarch64
>> - enable notifications via email
>>
>> Signed-off-by: Roger Meier <r.meier@siemens.com>
>> Cc: Wolfgang Denk <wd@denx.de>
>> Cc: Heiko Schocher <hs@denx.de>
>> Cc: Tom Rini <trini@ti.com>
>> Cc: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
>> Cc: Andreas F?rber <afaerber@suse.de>
>> Tested-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
>> Acked-by: Heiko Schocher <hs@denx.de>
>
> Applied to u-boot/master, thanks!
I wanted to add something to this file, so I set up my own travis-ci.org
account and made it run against my own github U-Boot repo "fork" to test
my change. However, most of the builds failed before I even modified
.travis.yml. For example:
> $ if [[ "${TOOLCHAIN}" == *arm* ]]; then sh eldk-eglibc-i686-arm-toolchain-gmae-5.4.sh -y ; fi
> Enter target directory for SDK (default: /opt/eldk-5.4/armv5te): /opt/eldk-5.4/armv5te
> You are about to install the SDK to "/opt/eldk-5.4/armv5te". Proceed[Y/n]?Y
> Sorry, you are not allowed to execute as root.
Do I need to perform some manual configuration of my
repo/branch/profile/... before this .travis.yml will work correctly
(container vs VM I wonder?), or perhaps obtain some kind of
authorization from the Travis CI admins? If so, if that could all be
documented in a comment at the top of .travis.yml that would be
extremely helpful. Bonus points if it can be handled simply be adding
extra configuration options into .travis.yml so that it "just works"
without manual steps.
next prev parent reply other threads:[~2016-02-03 16:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 19:22 [U-Boot] [PATCH] .travis.yml: rework according to new travis-ci infra Roger Meier
2016-01-26 0:46 ` Daniel Schwierzeck
2016-01-26 5:51 ` Heiko Schocher
2016-02-02 1:57 ` [U-Boot] " Tom Rini
2016-02-03 16:58 ` Stephen Warren [this message]
2016-02-04 9:30 ` Meier, Roger
2016-02-04 12:31 ` Daniel Schwierzeck
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=56B231AC.9040807@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=u-boot@lists.denx.de \
/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