From: stefan@agner.ch
To: yocto@yoctoproject.org, elizabeth.flanagan@intel.com
Cc: stefan@agner.ch
Subject: [yocto-autobuilder][PATCH v1 0/4] fixes for use with Angstrom
Date: Thu, 8 May 2014 18:44:24 +0200 [thread overview]
Message-ID: <cover.1399561605.git.stefan@agner.ch> (raw)
From: Stefan Agner <stefan@agner.ch>
Hi folks,
We plan to make use of the Yocto Autobuilder at Toradex. I successfully
deployed an installation, however since we distribute an Anstrom based
BSP I had to adjust some files. With those patches and a custom layer
configuration (not included since quite ugly) I'm able to build our BSP.
Would be good to have those changes upstream. Especially the new way to
preserve the order of builders is more generic, however maybe not yet
perfect. I needed this especially since I build some other stuff using
POBBC (plain old build bot configuration :-)).
Just as a general question: What is planned with the autobuilder in
general? Is there an integration planned with Toaster? As far as I can
see, since the build directory is recreated each time, this is not
really possible right now. It would need adjustment to the autobuilder
to start the toaster web interface for each builder, and clean/restart
builds in a way that doesn't interfere with Toaster. Any thoughts on
this?
--
Stefan
Stefan Agner (4):
GetDistroVersion.py support for Angstrom distro version
README: add high level overview, fix build slave description
master.py/botmaster.py: use builders list for builders order
GetDeployDir.py/PublishArtifacts.py: get deploy dir from bitbake
README | 8 ++--
README-NEW-AUTOBUILDER | 11 +++++
.../site-packages/autobuilder/Autobuilder.py | 17 ++++----
.../autobuilder/buildsteps/GetDeployDir.py | 47 +++++++++++++++++++++
.../autobuilder/buildsteps/GetDistroVersion.py | 7 +++-
.../autobuilder/buildsteps/PublishArtifacts.py | 48 ++++++++++++----------
.../buildbot/process/botmaster.py | 3 +-
.../buildbot/status/master.py | 12 +-----
8 files changed, 106 insertions(+), 47 deletions(-)
create mode 100644 lib/python2.7/site-packages/autobuilder/buildsteps/GetDeployDir.py
--
1.9.0
next reply other threads:[~2014-05-08 16:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 16:44 stefan [this message]
2014-05-08 16:44 ` [yocto-autobuilder][PATCH v1 1/4] GetDistroVersion.py support for Angstrom distro version stefan
2014-05-08 16:44 ` [yocto-autobuilder][PATCH v1 2/4] README: add high level overview, fix build slave description stefan
2014-05-08 16:44 ` [yocto-autobuilder][PATCH v1 3/4] master.py/botmaster.py: use builders list for builders order stefan
2014-05-08 16:44 ` [yocto-autobuilder][PATCH v1 4/4] GetDeployDir.py/PublishArtifacts.py: get deploy dir from bitbake stefan
2014-05-16 17:11 ` Flanagan, Elizabeth
2014-05-17 13:16 ` Stefan Agner
2014-05-15 13:03 ` [yocto-autobuilder][PATCH v1 0/4] fixes for use with Angstrom Stefan Agner
2014-05-15 15:32 ` Flanagan, Elizabeth
2014-05-17 13:31 ` Stefan Agner
2014-05-15 15:37 ` Flanagan, Elizabeth
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=cover.1399561605.git.stefan@agner.ch \
--to=stefan@agner.ch \
--cc=elizabeth.flanagan@intel.com \
--cc=yocto@yoctoproject.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 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.