From: Lianhao Lu <lianhao.lu@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PRService/meta V3 0/3] new PRService features in meta
Date: Tue, 10 Jan 2012 14:22:04 +0800 [thread overview]
Message-ID: <cover.1326176214.git.lianhao.lu@intel.com> (raw)
V3: Using event handler instead of new tasks to interfacing to bitbake.
V2: Using bb.fatal instead of bb.FuncFailed.
NOTE: This set of patches added supporting for new features in meta layer.
It should work together with another branch of patches in bitbake.
git://git.pokylinux.org/poky-contrib llu/PRService_bitbake
It supports the export/import AUTOPR values from/to PRservice to lockdown
the PR values for release. The typical usage scenario is:
1. UserA enabled the PRService and run buildings. The PRService will
record the AUTOPR values(which will be included in the finale PKGR) for
different packages the userA builds.
2. UserA runs "bitbake-prserv-tool export <file>" to export the AUTOPR
values from the current PRService into an exported inc file.
3. UserB gets the exported inc file and runs the command
"bitbake -R <exported file> target" to lockdown and reproduce the same AUTOPR
when generating packages.
4. UserB may run "bitbake-prserv-tool import <file>" to import the exported
AUTOPR values back into his own PRService. The AUTOPR values will be
incremented from there.
This set of changes also supports the per-recipe based PRSERV_HOST and
PRSERV_PORT.
This set of changes makes the basichash instead of the basic as the default
signature generator.
The following changes since commit fff18970706913e7fd7f4a119d798dddb44b388a:
Gary Thomas (1):
base-files: filesystems: fix mount order
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib llu/PRService_oecore
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=llu/PRService_oecore
Lianhao Lu (3):
meta/PRService: Added export/import fuctions.
package.bbclass: per recipe PRSERV_HOST support
conf/bitbake.conf: basichash as default signature.
meta/classes/package.bbclass | 21 +++++++-
meta/classes/prexport.bbclass | 45 ++++++++++++++++
meta/classes/primport.bbclass | 17 ++++++
meta/classes/prserv.bbclass | 36 +++++--------
meta/conf/bitbake.conf | 6 +-
meta/conf/prexport.conf | 1 +
meta/conf/primport.conf | 1 +
meta/lib/oe/prservice.py | 113 +++++++++++++++++++++++++++++++++++++++++
scripts/bitbake-prserv-tool | 57 +++++++++++++++++++++
9 files changed, 269 insertions(+), 28 deletions(-)
create mode 100644 meta/classes/prexport.bbclass
create mode 100644 meta/classes/primport.bbclass
create mode 100644 meta/conf/prexport.conf
create mode 100644 meta/conf/primport.conf
create mode 100644 meta/lib/oe/prservice.py
create mode 100755 scripts/bitbake-prserv-tool
next reply other threads:[~2012-01-10 6:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 6:22 Lianhao Lu [this message]
2012-01-10 6:22 ` [PRService/meta V3 1/3] meta/PRService: Added export/import fuctions Lianhao Lu
2012-01-10 6:22 ` [PRService/meta V3 2/3] package.bbclass: per recipe PRSERV_HOST support Lianhao Lu
2012-01-10 6:22 ` [PRService/meta V3 3/3] conf/bitbake.conf: basichash as default signature Lianhao Lu
2012-01-12 6:32 ` [PRService/meta V3 0/3] new PRService features in meta Saul Wold
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.1326176214.git.lianhao.lu@intel.com \
--to=lianhao.lu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox