All of lore.kernel.org
 help / color / mirror / Atom feed
From: Elizabeth Flanagan <elizabeth.flanagan@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] Add adt-installer-dev target for QA use
Date: Tue,  4 Sep 2012 17:56:29 -0700	[thread overview]
Message-ID: <cover.1346806132.git.elizabeth.flanagan@intel.com> (raw)

This is the first step in fixing the long standing QA complaint of having
no good way of testing ADTREPO:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=2800
https://bugzilla.yoctoproject.org/show_bug.cgi?id=1877
https://bugzilla.yoctoproject.org/show_bug.cgi?id=2718

This target will be added to most autobuilder buildouts and the autobuilder
will populate adtrepo-dev from the artifacts. This ensures that released build
artifacts are jailed off and cannot be accidentally destroyed while ensuring 
QA has something to test.

The following changes since commit 99c85ba93075a1aff789cafabbacf42e6a93bd32:

  build-appliance-image: Update to latest poky master (2012-09-04 18:04:40 +0100)

are available in the git repository at:
  git://git.yoctoproject.org/poky-contrib eflanagan/adtfix
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=eflanagan/adtfix

Elizabeth Flanagan (1):
  adt-installer: Add adt-installer-dev.bb

 .../installer/adt-installer-dev_1.0.bb             |   26 ++++++++++++++++++++
 .../installer/adt-installer/adt_installer.conf     |    2 +-
 2 files changed, 27 insertions(+), 1 deletions(-)
 create mode 100644 meta/recipes-devtools/installer/adt-installer-dev_1.0.bb

-- 
1.7.5.4




             reply	other threads:[~2012-09-05  1:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-05  0:56 Elizabeth Flanagan [this message]
2012-09-05  0:56 ` [PATCH 1/1] adt-installer: Add adt-installer-dev.bb Elizabeth Flanagan
2012-09-05  1:12 ` [PATCH 0/1] Add adt-installer-dev target for QA use 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.1346806132.git.elizabeth.flanagan@intel.com \
    --to=elizabeth.flanagan@intel.com \
    --cc=openembedded-core@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.