All of lore.kernel.org
 help / color / mirror / Atom feed
From: Klaus Schwarzkopf <schwarzkopf@sensortherm.de>
To: openembedded-devel@lists.openembedded.org
Subject: buildserver
Date: Fri, 19 Nov 2010 10:46:33 +0100	[thread overview]
Message-ID: <4CE64779.3020802@sensortherm.de> (raw)

Hi,

i have some problems with the ti recipes, see my emails on the list.

The two problems are:
* the recipes are out of date and don't work.
* the recipes can't download the source files.

My idea is, to have an buildserver. On every commit (every night or 
every week), the buildserver download the sources and build the recipe.

If the server builds the recipe successful, it copy the source files to 
the webserver.

If the builds fails, the person how committed the recipe recieve a email 
with the log files.

What do you think about my idea?

Greetings

Klaus




             reply	other threads:[~2010-11-19  9:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-19  9:46 Klaus Schwarzkopf [this message]
2010-11-19 10:37 ` buildserver Koen Kooi
2010-11-19 11:48   ` buildserver Klaus Schwarzkopf
2010-11-20 13:29   ` buildserver Klaus Schwarzkopf
2010-11-19 10:42 ` buildserver Yury Bushmelev
2010-11-19 11:24   ` buildserver Martin Jansa
2010-11-19 12:21     ` buildserver Frans Meulenbroeks
2010-11-19 11:55   ` buildserver Klaus Schwarzkopf
2010-11-19 12:04   ` buildserver Dvorkin Dmitry
2010-11-20 13:49   ` buildserver Klaus Schwarzkopf
2010-11-21 18:08     ` buildserver Chris Larson
2010-11-22  8:38       ` buildserver Klaus Schwarzkopf
2010-11-22  8:56         ` buildserver Frans Meulenbroeks
2010-11-22 15:14           ` buildserver Klaus Schwarzkopf
2010-11-22 17:25             ` buildserver Frans Meulenbroeks
2010-11-22 17:31               ` buildserver Eric Bénard
2010-11-22 18:21                 ` buildserver Frans Meulenbroeks
2010-11-22 18:41                   ` buildserver Eric Bénard

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=4CE64779.3020802@sensortherm.de \
    --to=schwarzkopf@sensortherm.de \
    --cc=openembedded-devel@lists.openembedded.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.