summaryrefslogtreecommitdiff
path: root/meta/classes/buildhistory.bbclass
AgeCommit message (Collapse)AuthorFiles
2012-01-06classes/buildhistory: remove redundant package history checking stubPaul Eggleton1
The code that would have gone here has been superseded by the buildhistory analysis functionality implemented in meta/lib/oe/buildhistory_analysis.py and scripts/buildhistory-diff, so remove it. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2012-01-06classes/buildhistory: make the package version backwards error non-fatalPaul Eggleton1
Just make it a bb.error when a package version goes backwards, it doesn't make sense to fail the build immediately; the error(s) will still be reflected in bitbake's exit code. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2012-01-06classes/buildhistory: add hostname to commit messagePaul Eggleton1
If we're building on multiple hosts then it's useful to have the hostname in the commit message. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2012-01-03buildhistory: improve git commit robustnessPaul Eggleton1
* Check if BUILDHISTORY_DIR exists before doing anything with it, in case no tasks that would have created it have executed * Ensure the git repo in BUILDHISTORY_DIR is initialised with "git init" before attempting to do anything with it * Check if any files have been added or changed before adding and committing, to avoid an error from "git commit" Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2012-01-02buildhistory: avoid quoting issues with the layer list for build-idChristopher Larson1
--4ef4ab1d_66334873_12d0c Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline The layer list is multiline, and includes quotes, so including it within quotes is problematic, particularly if the revision includes characters which are not valid outside of a quoted string in shell. To reproduce this failure: do a build with an scm layer not on a branch. Signed-off-by: Christopher Larson <chris_larson@mentor.com (mailto:chris_larson@mentor.com)>
2011-12-06buildhistory bbclass: avoid absolute paths for files-in-image.txt to avoid ↵Koen Kooi1
diff churn when relocating TMPDIR Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-12-05classes/buildhistory: do not save old packagehistory files by defaultPaul Eggleton1
Disable storing package history as version named files unless BUILDHISTORY_KEEP_VERSIONS is set to 1; otherwise the adds of these files that duplicate what is already in git anyway is just noise in the git log. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-12-05classes/buildhistory: merge in package history functionalityPaul Eggleton1
Include package history collection from packagehistory.bbclass (thus superseding it). The only change is to store package history under BUILDHISTORY_DIR/packages and rename one of the functions. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2011-12-05classes/buildhistory: add new output history collection classPaul Eggleton1
Create a new build output history reporting class, using testlab.bbclass from meta-oe as a base. This records information from images produced by the build process in text files structured suitably for tracking within a git repository, thus enabling monitoring of changes over time. Build history collection can be enabled simply by adding the following to your local.conf: INHERIT += "buildhistory" The output after a build can then be found in BUILDHISTORY_DIR (defaults to TMPDIR/buildhistory). If you set up this directory as a git repository and set BUILDHISTORY_COMMIT to "1" in local.conf, the build history data will be committed on every build. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2011-12-01Revert "classes/buildhistory: add new output history collection class"Richard Purdie1
This reverts commit 508ff624fea705eb93cf2cc1e0c9c42cb817acf8. RP accidentally pulled the wrong commit in, it was supposed to be a *package*history bbclass change.
2011-12-01classes/buildhistory: add new output history collection classPaul Eggleton1
Create a new build output history reporting class, using testlab.bbclass from meta-oe and packagehistory.bbclass as a base. This records information from packages and images output from the build process in text files structured suitably for tracking within a git repository, thus enabling monitoring of changes over time. Build history collection can be enabled simply by adding the following to your local.conf: INHERIT += "buildhistory" The output after a build can then be found in BUILDHISTORY_DIR (defaults to TMPDIR/buildhistory). If you set up this directory as a git repository and set BUILDHISTORY_COMMIT to "1" in local.conf, the build history data will be committed on every build. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>