Buildhistory - Revision history

PaulEggleton: Remove most of the content and point to updated version in the reference manual

2013-07-18T11:05:58Z

Remove most of the content and point to updated version in the reference manual

PaulEggleton: Add screenshot of web UI

2012-10-09T23:08:44Z

Add screenshot of web UI

← Older revision		Revision as of 23:08, 9 October 2012
Line 144:		Line 144:
	* PR changed from "r0" to "r1"		* PR changed from "r0" to "r1"
	* PV changed from "0.1.10" to "0.1.12"		* PV changed from "0.1.10" to "0.1.12"

			[[File:Buildhistory-web1.png\|200px\|thumb\|right\|Buildhistory web UI]]

	=== Web UI ===		=== Web UI ===
Line 152:		Line 154:

	For more details please see the README file in the repository.		For more details please see the README file in the repository.

			<br style="clear: both" />

	== Disabling buildhistory temporarily ==		== Disabling buildhistory temporarily ==

PaulEggleton: Add link to newly released web UI

2012-10-08T23:31:07Z

Add link to newly released web UI

← Older revision		Revision as of 23:31, 8 October 2012
Line 125:		Line 125:

	== Analysing changes ==		== Analysing changes ==

			=== Command line ===

	To see any changes that have occurred (assuming you have <tt>BUILDHISTORY_COMMIT = "1"</tt>) you can simply use <tt>git log -p</tt> or some other method of viewing the git history, however this will show changes that aren't significant e.g. a package changing in size by a few bytes. However, there is a command-line tool called <tt>buildhistory-diff</tt> which will query the git repository and print just the differences that might be significant in human-readable form. For example:		To see any changes that have occurred (assuming you have <tt>BUILDHISTORY_COMMIT = "1"</tt>) you can simply use <tt>git log -p</tt> or some other method of viewing the git history, however this will show changes that aren't significant e.g. a package changing in size by a few bytes. However, there is a command-line tool called <tt>buildhistory-diff</tt> which will query the git repository and print just the differences that might be significant in human-readable form. For example:
Line 143:		Line 145:
	* PV changed from "0.1.10" to "0.1.12"		* PV changed from "0.1.10" to "0.1.12"

	A web-based frontend for processing and flagging these reported changes is ~~currently [~~http://~~bugzilla~~.yoctoproject.org/~~show_bug~~.cgi~~?id=1890~~ in ~~development]~~.		=== Web UI ===

			A web-based frontend for processing and flagging these reported changes is also available:

			http://git.yoctoproject.org/cgit/cgit.cgi/buildhistory-web/

			For more details please see the README file in the repository.

	== Disabling buildhistory temporarily ==		== Disabling buildhistory temporarily ==

PaulEggleton: Fix typo

2012-08-02T09:49:22Z

Fix typo

← Older revision		Revision as of 09:49, 2 August 2012
Line 1:		Line 1:
	When upgrading a recipe to a new version of an upstream software package, or trying out new configuration options, subtle changes can occur in the output that may not be noticed until later. For example, a new version of a piece of software might introduce an optional dependency on another library which is ~~autodected~~; if that library has already been built when the software is building, then the software will link to that library and it will now be pulled into your image with the software even if you didn't want it.		When upgrading a recipe to a new version of an upstream software package, or trying out new configuration options, subtle changes can occur in the output that may not be noticed until later. For example, a new version of a piece of software might introduce an optional dependency on another library which is auto-detected; if that library has already been built when the software is building, then the software will link to that library and it will now be pulled into your image with the software even if you didn't want it.

	The buildhistory class was created to highlight unexpected and possibly unwanted changes such as these in the build system output. It will record information about the contents of each package (e.g. size, dependencies, list of files) and image (e.g. packages and files in the image), and commit it to a git repository so you can see when something changes.		The buildhistory class was created to highlight unexpected and possibly unwanted changes such as these in the build system output. It will record information about the contents of each package (e.g. size, dependencies, list of files) and image (e.g. packages and files in the image), and commit it to a git repository so you can see when something changes.

PaulEggleton at 15:43, 1 June 2012

2012-06-01T15:43:24Z

← Older revision		Revision as of 15:43, 1 June 2012
Line 142:		Line 142:
	* PR changed from "r0" to "r1"		* PR changed from "r0" to "r1"
	* PV changed from "0.1.10" to "0.1.12"		* PV changed from "0.1.10" to "0.1.12"

			A web-based frontend for processing and flagging these reported changes is currently [http://bugzilla.yoctoproject.org/show_bug.cgi?id=1890 in development].

	== Disabling buildhistory temporarily ==		== Disabling buildhistory temporarily ==

PaulEggleton at 15:33, 1 June 2012

2012-06-01T15:33:28Z

← Older revision		Revision as of 15:33, 1 June 2012
Line 142:		Line 142:
	* PR changed from "r0" to "r1"		* PR changed from "r0" to "r1"
	* PV changed from "0.1.10" to "0.1.12"		* PV changed from "0.1.10" to "0.1.12"

			== Disabling buildhistory temporarily ==

			Adding and removing the inherit of buildhistory from your configuration can change the do_package task checksums, which if you are using the OEBasicHash signature generator (the default for some distro configurations) will result in the packaging tasks being re-run each time you do this. To turn off buildhistory functionality without causing this to happen you can just add the following to your local.conf:

			BUILDHISTORY_FEATURES = ""

			== Usage for image content analysis only ==

			buildhistory outputs image information, including dependency graphs, so you can see easily why something was pulled into the image. If you are just interested in this information and not collecting history or any package information, you can do this by adding the following to your local.conf:

			INHERIT += "buildhistory"
			BUILDHISTORY_COMMIT = "0"
			BUILDHISTORY_FEATURES = "image"

			== Example repositories ==

			History data using buildhistory is already being collected from various autobuilders and published:

			* [http://github.com/Angstrom-distribution/buildhistory Angstrom]
			* [http://git.yoctoproject.org/cgit/cgit.cgi/poky-buildhistory/ Poky]
			* [http://git.shr-project.org/git/?p=buildhistory.git;a=summary SHR]

PaulEggleton at 12:21, 9 February 2012

2012-02-09T12:21:32Z

← Older revision		Revision as of 12:21, 9 February 2012
Line 106:		Line 106:
	\|}		\|}

	Note that package information is able to be gathered and produced even if packaging is disabled for the final image.		Note that installed package information is able to be gathered and produced even if packaging is disabled for the final image.

	An example image-info.txt:		An example image-info.txt:

PaulEggleton at 12:21, 9 February 2012

2012-02-09T12:21:15Z

← Older revision		Revision as of 12:21, 9 February 2012
Line 105:		Line 105:
	\|\|installed-packages.txt\|\|A list of installed packages (full package filename)		\|\|installed-packages.txt\|\|A list of installed packages (full package filename)
	\|}		\|}

			Note that package information is able to be gathered and produced even if packaging is disabled for the final image.

	An example image-info.txt:		An example image-info.txt:

PaulEggleton at 12:20, 9 February 2012

2012-02-09T12:20:09Z

← Older revision		Revision as of 12:20, 9 February 2012
Line 103:		Line 103:
	\|\|installed-package-sizes.txt\|\|A list of installed packages ordered by size		\|\|installed-package-sizes.txt\|\|A list of installed packages ordered by size
	\|-		\|-
	\|\|installed-packages.txt\|\|A list of ~~installled~~ packages (full package filename)		\|\|installed-packages.txt\|\|A list of installed packages (full package filename)
	\|}		\|}

PaulEggleton at 12:18, 9 February 2012

2012-02-09T12:18:03Z

← Older revision		Revision as of 12:18, 9 February 2012
Line 24:		Line 24:
	\| `-- atom_pc		\| `-- atom_pc
	\| `-- eglibc		\| `-- eglibc
	\| `-- ~~pinpoint~~-image		\| `-- core-image-minimal
	\| \|-- build-id		\| \|-- build-id
	\| \|-- depends.dot		\| \|-- depends.dot