Obsolete - Yocto Buildbot Autobuilder Discussions - Revision history

Michael Opdenacker: Michael Opdenacker moved page Yocto Buildbot Autobuilder Discussions to Obsolete - Yocto Buildbot Autobuilder Discussions: Obsolete contents, can be deleted

2022-01-14T18:25:25Z

Michael Opdenacker moved page Yocto Buildbot Autobuilder Discussions to Obsolete - Yocto Buildbot Autobuilder Discussions: Obsolete contents, can be deleted

← Older revision	Revision as of 18:25, 14 January 2022
(No difference)

Michael Opdenacker: Removed contents - Can be deleted

2022-01-14T18:24:52Z

Removed contents - Can be deleted

Show changes

Jay7: /* Discussion with pidge/Jay7/ka6sox on #yocto-buildstats */

2011-04-27T17:02:58Z

Discussion with pidge/Jay7/ka6sox on #yocto-buildstats

Show changes

Eflanagan: /* Build statistics visualization use cases */

2011-04-27T16:39:54Z

Build statistics visualization use cases

← Older revision		Revision as of 16:39, 27 April 2011
Line 22:		Line 22:
	== Build statistics visualization use cases ==		== Build statistics visualization use cases ==

	- I want to see 20111109 and 20111110 and compare the time it took to build foo		* I want to see 20111109 and 20111110 and compare the time it took to build foo
	- I want to see 20111109 and 20111110 and compare the time it took to do_rootfs		* I want to see 20111109 and 20111110 and compare the time it took to do_rootfs
	- I want to see 20111109 and 20111110 and 20090404 and compare the time it took to do everything that took more than 4 seconds		* I want to see 20111109 and 20111110 and 20090404 and compare the time it took to do everything that took more than 4 seconds
	- I just want to see a graph similar to the pybootchart graph of 20110101 of every bitbake task that took more than 8 seconds		* I just want to see a graph similar to the pybootchart graph of 20110101 of every bitbake task that took more than 8 seconds
	- I want to run this standalone. I want this to be an easy setup so I can look at http://localhost/buildstats, have it configured to look at my buildstats dir and be able to get graphs on that.		* I want to run this standalone. I want this to be an easy setup so I can look at http://localhost/buildstats, have it configured to look at my buildstats dir and be able to get graphs on that.
	- I want to be able to run this using my autobuilder.		* I want to be able to run this using my autobuilder.
	- I want to have the option of allowing others to upload their buildstats (for OE mainly) similar to how OEStats does it		* I want to have the option of allowing others to upload their buildstats (for OE mainly) similar to how OEStats does it

	== Use cases ==		== Use cases ==

Eflanagan at 16:39, 27 April 2011

2011-04-27T16:39:21Z

Show changes

Jay7: /* Use cases */ add section

2011-04-26T21:12:18Z

Use cases: add section

← Older revision		Revision as of 21:12, 26 April 2011
Line 18:		Line 18:

	NOTE: May be terminology master-slave should be replaced with something because of political correctness.		NOTE: May be terminology master-slave should be replaced with something because of political correctness.

			== Use cases ==
			* Alice is started build on home machine. It fails and show URL where full error info is located. Alice show this URL on irc channel/ML and got help. If Alice doing build offline she may run some tool (push-build-results) when online to upload stats and errors to server and get that URL.
			* Bob is a developer. He is started build which is failed on some package. He is going to Yocto buildstats server to check what builds of that package was succeeded (if any).
			* Claudia have strong machine that mostly idling. She want to allow Yocto project to run builds on her machine when it is idle (at night e.g.).
			* Daniel is core developer but have slow machine under his hands. So he is going to Yocto's build server and requesting build from his git repo/branch and some special build environment. Build master rearrange tasks and put his task to start of queue. After build it sends build short info to Daniel via email/jabber/irc.
			* Elizabeth is sysadmin at some big company which doing some products based on Yocto. Company have large buildfarm. Elizabeth want to manage large set of builds from her workstation or notebook. She have installed build slaves on farm nodes and setup build master on some server. So how she may control it over web interface - add/remove/change builds parameters, wire some builds to nodes, look at build results.

	== Requirements ==		== Requirements ==

Jay7: /* Technical part */

2011-03-22T01:05:39Z

Technical part

← Older revision		Revision as of 01:05, 22 March 2011
Line 71:		Line 71:
	# BuildBot http://trac.buildbot.net/ (used by Yocto)		# BuildBot http://trac.buildbot.net/ (used by Yocto)
	# Jenkins http://jenkins-ci.org/, remote access API: http://wiki.jenkins-ci.org/display/JENKINS/Remote+access+API		# Jenkins http://jenkins-ci.org/, remote access API: http://wiki.jenkins-ci.org/display/JENKINS/Remote+access+API
			# LAVA https://wiki.linaro.org/Platform/Validation/LAVA

	== Discussions ==		== Discussions ==

Jay7: /* Discussion with asac on #linaro */

2011-03-22T01:02:16Z

Discussion with asac on #linaro

Jay7: /* Discussions */ Added discussion with asac on #linaro

2011-03-22T01:01:15Z

Discussions: Added discussion with asac on #linaro

← Older revision		Revision as of 01:01, 22 March 2011
Line 165:		Line 165:
	[00:00] <Jay7> but now it does not matters :)<br />		[00:00] <Jay7> but now it does not matters :)<br />
	[00:01] <ka6sox> most important to me are the definitions of what data is important and not.<br />		[00:01] <ka6sox> most important to me are the definitions of what data is important and not.<br />


			=== Discussion with asac on #linaro ===
			[03:36] <Jay7> seems you are working on build stats tools as well :)
			[03:37] * Jay7 have doing some prototype for Yocto/OE
			[03:37] <Jay7> https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions
			[03:37] <Jay7> here are my ideas
			[03:38] <asac> Jay7: our stuff is a cloud setup ... and assume eversything is cross build ... so we dont need slaves querying for new builds
			[03:39] <asac> we just spin up an instance, build, kill it
			[03:39] <asac> oh its build-testing ;)
			[03:39] <asac> hehe
			[03:39] <asac> nevermind
			[03:39] * asac cannot read
			[03:39] <Jay7> there is a lot of things combined
			[03:40] <Jay7> building/testing/collecting statistics/etc
			[03:40] <asac> Jay7: whats the status of that project?
			[03:40] <asac> Jay7: sure, building is often part of testing/validation
			[03:40] <Jay7> asac: 3 different clients, 2 different dead servers and no master/slave :)
			[03:41] <asac> lol
			[03:41] <Jay7> seems we are starting from scratch
			[03:41] <asac> Jay7: who is leading that effort?
			[03:41] <asac> Jay7: why dont you join lava ;)
			[03:41] <Jay7> lava?
			[03:41] <asac> thats our testing/validation infrastructure
			[03:41] <asac> feels quite similar
			[03:41] <Jay7> I'm slowly trying to prototype this
			[03:41] <Jay7> there are 2 people around as well
			[03:42] <asac> we currently focus on image testing, benchmarking etc.
			[03:42] <Jay7> asac: where I can read about lava? :)
			[03:42] <asac> Jay7: we have a team of 6 ;)
			[03:42] <asac> Jay7: https://wiki.linaro.org/Platform/Validation/LAVA
			[03:43] <Jay7> asac: your team are paid to work on this I suspect ;)
			[03:43] <asac> but i think building could be rather done with something like our build service and then injected into the test farm. focus is realyl about executing tests/benchmarks on various images on various boards etc.
			[03:43] <asac> Jay7: yes, thats why i think its better to join here
			[03:43] <Jay7> well
			[03:43] <Jay7> pidge have talk on ELC about this
			[03:44] <Jay7> pidge == Elisabeth Flanagan
			[03:44] <Jay7> from Yocto side
			[03:44] <asac> funny
			[03:44] <asac> plars also talks about LAVA there ;)
			[03:44] <Jay7> cool
			[03:44] <Jay7> I should say pidge about this :)
			[03:44] <asac> is she the projet owner?
			[03:45] <asac> i think we should discuss, yes.
			[03:45] <asac> we build it for android and ubuntu on ARM atm
			[03:45] <asac> so adding another thing would be just "one" more
			[03:45] <Jay7> asac: yes, it would be great imho

Jay7: /* Client */

2011-03-15T12:13:26Z

Client

← Older revision		Revision as of 12:13, 15 March 2011
Line 33:		Line 33:
	** builder name/id		** builder name/id
	** build type (clean/incremental)		** build type (clean/incremental)
	** build status (successfull/failed)
	* report to server per-package		* report to server per-package
	** package name		** package name

← Older revision		Revision as of 01:02, 22 March 2011
Line 168:		Line 168:

	=== Discussion with asac on #linaro ===		=== Discussion with asac on #linaro ===
	[03:36] <Jay7> seems you are working on build stats tools as well :)		[03:36] <Jay7> seems you are working on build stats tools as well :)<br />
	[03:37] * Jay7 have doing some prototype for Yocto/OE		[03:37] * Jay7 have doing some prototype for Yocto/OE<br />
	[03:37] <Jay7> https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions		[03:37] <Jay7> https://wiki.yoctoproject.org/wiki/Yocto_Buildbot_Autobuilder_Discussions<br />
	[03:37] <Jay7> here are my ideas		[03:37] <Jay7> here are my ideas<br />
	[03:38] <asac> Jay7: our stuff is a cloud setup ... and assume eversything is cross build ... so we dont need slaves querying for new builds		[03:38] <asac> Jay7: our stuff is a cloud setup ... and assume eversything is cross build ... so we dont need slaves querying for new builds<br />
	[03:39] <asac> we just spin up an instance, build, kill it		[03:39] <asac> we just spin up an instance, build, kill it<br />
	[03:39] <asac> oh its build-testing ;)		[03:39] <asac> oh its build-testing ;)<br />
	[03:39] <asac> hehe		[03:39] <asac> hehe<br />
	[03:39] <asac> nevermind		[03:39] <asac> nevermind<br />
	[03:39] * asac cannot read		[03:39] * asac cannot read<br />
	[03:39] <Jay7> there is a lot of things combined		[03:39] <Jay7> there is a lot of things combined<br />
	[03:40] <Jay7> building/testing/collecting statistics/etc		[03:40] <Jay7> building/testing/collecting statistics/etc<br />
	[03:40] <asac> Jay7: whats the status of that project?		[03:40] <asac> Jay7: whats the status of that project?<br />
	[03:40] <asac> Jay7: sure, building is often part of testing/validation		[03:40] <asac> Jay7: sure, building is often part of testing/validation<br />
	[03:40] <Jay7> asac: 3 different clients, 2 different dead servers and no master/slave :)		[03:40] <Jay7> asac: 3 different clients, 2 different dead servers and no master/slave :)<br />
	[03:41] <asac> lol		[03:41] <asac> lol<br />
	[03:41] <Jay7> seems we are starting from scratch		[03:41] <Jay7> seems we are starting from scratch<br />
	[03:41] <asac> Jay7: who is leading that effort?		[03:41] <asac> Jay7: who is leading that effort?<br />
	[03:41] <asac> Jay7: why dont you join lava ;)		[03:41] <asac> Jay7: why dont you join lava ;)<br />
	[03:41] <Jay7> lava?		[03:41] <Jay7> lava?<br />
	[03:41] <asac> thats our testing/validation infrastructure		[03:41] <asac> thats our testing/validation infrastructure<br />
	[03:41] <asac> feels quite similar		[03:41] <asac> feels quite similar<br />
	[03:41] <Jay7> I'm slowly trying to prototype this		[03:41] <Jay7> I'm slowly trying to prototype this<br />
	[03:41] <Jay7> there are 2 people around as well		[03:41] <Jay7> there are 2 people around as well<br />
	[03:42] <asac> we currently focus on image testing, benchmarking etc.		[03:42] <asac> we currently focus on image testing, benchmarking etc.<br />
	[03:42] <Jay7> asac: where I can read about lava? :)		[03:42] <Jay7> asac: where I can read about lava? :)<br />
	[03:42] <asac> Jay7: we have a team of 6 ;)		[03:42] <asac> Jay7: we have a team of 6 ;)<br />
	[03:42] <asac> Jay7: https://wiki.linaro.org/Platform/Validation/LAVA		[03:42] <asac> Jay7: https://wiki.linaro.org/Platform/Validation/LAVA<br />
	[03:43] <Jay7> asac: your team are paid to work on this I suspect ;)		[03:43] <Jay7> asac: your team are paid to work on this I suspect ;)<br />
	[03:43] <asac> but i think building could be rather done with something like our build service and then injected into the test farm. focus is realyl about executing tests/benchmarks on various images on various boards etc.		[03:43] <asac> but i think building could be rather done with something like our build service and then injected into the test farm. focus is realyl about executing tests/benchmarks on various images on various boards etc.<br />
	[03:43] <asac> Jay7: yes, thats why i think its better to join here		[03:43] <asac> Jay7: yes, thats why i think its better to join here<br />
	[03:43] <Jay7> well		[03:43] <Jay7> well<br />
	[03:43] <Jay7> pidge have talk on ELC about this		[03:43] <Jay7> pidge have talk on ELC about this<br />
	[03:44] <Jay7> pidge == Elisabeth Flanagan		[03:44] <Jay7> pidge == Elisabeth Flanagan<br />
	[03:44] <Jay7> from Yocto side		[03:44] <Jay7> from Yocto side<br />
	[03:44] <asac> funny		[03:44] <asac> funny<br />
	[03:44] <asac> plars also talks about LAVA there ;)		[03:44] <asac> plars also talks about LAVA there ;)<br />
	[03:44] <Jay7> cool		[03:44] <Jay7> cool<br />
	[03:44] <Jay7> I should say pidge about this :)		[03:44] <Jay7> I should say pidge about this :)<br />
	[03:44] <asac> is she the projet owner?		[03:44] <asac> is she the projet owner?<br />
	[03:45] <asac> i think we should discuss, yes.		[03:45] <asac> i think we should discuss, yes.<br />
	[03:45] <asac> we build it for android and ubuntu on ARM atm		[03:45] <asac> we build it for android and ubuntu on ARM atm<br />
	[03:45] <asac> so adding another thing would be just "one" more		[03:45] <asac> so adding another thing would be just "one" more<br />
	[03:45] <Jay7> asac: yes, it would be great imho		[03:45] <Jay7> asac: yes, it would be great imho<br />