Contribute to Toaster - Revision history

David Reyna at 06:17, 15 November 2025

2025-11-15T06:17:44Z

← Older revision		Revision as of 06:17, 15 November 2025
Line 13:		Line 13:
	For development of Toaster we recommend setting up a local install of Toaster. Installation instructions are available in the main [https://docs.yoctoproject.org/toaster-manual/index.html Toaster documentation]		For development of Toaster we recommend setting up a local install of Toaster. Installation instructions are available in the main [https://docs.yoctoproject.org/toaster-manual/index.html Toaster documentation]

	== Submitting patches ==		== Submitting patches (bitbake-setup) ==

	~~Publishing your patches to Toaster is a two step process.~~
	~~# Sending patches to the [https://lists.yoctoproject.org/listinfo/toaster/\| Toaster mailing list] for review~~
	~~# Submitting the patches that you reviewed to the upstream repository~~

	By submitting your patches first to the Toaster mailing list, you can be sure the patches are reviewed by the people in the community who are familiar with the Toaster source code, and who have experience developing web applications.

	~~That also means that, by the time the patches are submitted to the upstream mailing lists, they are in pretty good shape. That helps the project maintainers, and hopefully also helps you.~~

	Toaster code lives in Bitbake repository at [http://git.openembedded.org/bitbake/\|http://git.openembedded.org/bitbake/].		Toaster code lives in Bitbake repository at [http://git.openembedded.org/bitbake/\|http://git.openembedded.org/bitbake/].
	All contributions must be upstreamed to the Bitbake repository in order to make it to the "master" branch of the poky/ repository.		All contributions must be upstreamed to the Bitbake repository in order to make it to the "master" branch of the poky/ repository.

	=== Workflow ~~(bitbake-setup)~~ ===		=== Workflow ===
	<br />		<br />
	1) Download master branch of the yocto project		1) Download master branch of the yocto project
Line 80:		Line 72:

	<br />		<br />
	~~7) Send your~~ patch ~~to the bitbake mailing list~~
			=== Submitting patch for integration into Bitbake ===

	<strong>Email list:</strong> bitbake-devel@lists.openembedded.org		<strong>Email list:</strong> bitbake-devel@lists.openembedded.org
Line 89:		Line 82:

	<pre>		<pre>
	TO: bitbake-devel@lists.openembedded.org		TO : bitbake-devel@lists.openembedded.org
	SUBJECT: [bitbake-devel][PATCH] toaster: support bitbake-setup		SUBJECT: [bitbake-devel][PATCH] toaster: support bitbake-setup
	CONTENT:		CONTENT:
Line 108:		Line 101:
	</pre>		</pre>

	== ~~Workflow~~ (Poky Classic, OBSOLETE) ==		== Submitting patches (Poky Classic, OBSOLETE) ==

			Publishing your patches to Toaster is a two step process.
			# Sending patches to the [https://lists.yoctoproject.org/listinfo/toaster/\| Toaster mailing list] for review
			# Submitting the patches that you reviewed to the upstream repository

			By submitting your patches first to the Toaster mailing list, you can be sure the patches are reviewed by the people in the community who are familiar with the Toaster source code, and who have experience developing web applications.

			That also means that, by the time the patches are submitted to the upstream mailing lists, they are in pretty good shape. That helps the project maintainers, and hopefully also helps you.

			Toaster code lives in Bitbake repository at [http://git.openembedded.org/bitbake/\|http://git.openembedded.org/bitbake/].
			All contributions must be upstreamed to the Bitbake repository in order to make it to the "master" branch of the poky/ repository.

			=== Workflow ===
	To contribute to toaster you will also need authorization to write to the upstream yocto project repository. Contact a member of the toaster team for details.		To contribute to toaster you will also need authorization to write to the upstream yocto project repository. Contact a member of the toaster team for details.

David Reyna at 06:08, 15 November 2025

2025-11-15T06:08:38Z

← Older revision		Revision as of 06:08, 15 November 2025
Line 108:		Line 108:
	</pre>		</pre>

	=== Workflow (Poky Classic, OBSOLETE) ===		== Workflow (Poky Classic, OBSOLETE) ==
	To contribute to toaster you will also need authorization to write to the upstream yocto project repository. Contact a member of the toaster team for details.		To contribute to toaster you will also need authorization to write to the upstream yocto project repository. Contact a member of the toaster team for details.

David Reyna: Add plain workflow for bitbake-setup model

2025-11-15T06:07:42Z

Add plain workflow for bitbake-setup model

@@ Line 26: / Line 26: @@
 All contributions must be upstreamed to the Bitbake repository in order to make it to the "master" branch of the poky/ repository.
-=== Workflow ===
+=== Workflow (bitbake-setup) ===
 To contribute to toaster you will also need authorization to write to the upstream yocto project repository.  Contact a member of the toaster team for details.

David Reyna at 19:05, 1 December 2023

2023-12-01T19:05:55Z

← Older revision		Revision as of 19:05, 1 December 2023
Line 11:		Line 11:
	== Set up the local repository ==		== Set up the local repository ==

	For development of Toaster we recommend setting up a local install of Toaster. Installation instructions are available in the main [https://docs.yoctoproject.org~~/dunfell~~/toaster-manual/~~toaster-manual-setup-and-use~~.html~~#starting-toaster-for-local-development~~ Toaster documentation]		For development of Toaster we recommend setting up a local install of Toaster. Installation instructions are available in the main [https://docs.yoctoproject.org/toaster-manual/index.html Toaster documentation]

	== Submitting patches ==		== Submitting patches ==

MichaelHalstead: Updating dead link

2023-11-30T21:53:33Z

Updating dead link

← Older revision		Revision as of 21:53, 30 November 2023
Line 11:		Line 11:
	== Set up the local repository ==		== Set up the local repository ==

	For development of Toaster we recommend setting up a local install of Toaster. Installation instructions are available in the main [~~http~~://~~www~~.yoctoproject.org/~~docs/latest~~/toaster-manual/toaster-manual.html#toaster-~~manual~~-~~start~~ Toaster documentation]		For development of Toaster we recommend setting up a local install of Toaster. Installation instructions are available in the main [https://docs.yoctoproject.org/dunfell/toaster-manual/toaster-manual-setup-and-use.html#starting-toaster-for-local-development Toaster documentation]

	== Submitting patches ==		== Submitting patches ==

David Reyna: /* Workflow */

2022-03-12T06:56:52Z

Workflow

← Older revision		Revision as of 06:56, 12 March 2022
Line 33:		Line 33:

	2) Add poky-contrib to the local repository you set up above		2) Add poky-contrib to the local repository you set up above
	<code> ~~[old]~~ git remote add poky-contrib ssh://git@~~git.yoctoproject.org/poky-contrib </code>~~		<code> git remote add poky-contrib ssh://git@push.yoctoproject.org/poky-contrib </code>
	~~<code> git remote add poky-contrib https://git~~.yoctoproject.org~~/git~~/poky-contrib </code>

	3) Fetch the poky-contrib branches		3) Fetch the poky-contrib branches

David Reyna: /* Workflow */

2022-03-08T17:56:59Z

Workflow

← Older revision		Revision as of 17:56, 8 March 2022
Line 33:		Line 33:

	2) Add poky-contrib to the local repository you set up above		2) Add poky-contrib to the local repository you set up above
	<code> git remote add poky-contrib ssh://git@git.yoctoproject.org/poky-contrib </code>		<code> [old] git remote add poky-contrib ssh://git@git.yoctoproject.org/poky-contrib </code>
			<code> git remote add poky-contrib https://git.yoctoproject.org/git/poky-contrib </code>

	3) Fetch the poky-contrib branches		3) Fetch the poky-contrib branches

David Reyna at 06:03, 30 June 2018

2018-06-30T06:03:42Z

← Older revision		Revision as of 06:03, 30 June 2018
Line 474:		Line 474:
	** Use an application like "sqlitebrowser" to examine the tables and records		** Use an application like "sqlitebrowser" to examine the tables and records
	** Use a Python script to find and dump desired database records (see http://events.linuxfoundation.org/sites/events/files/slides/BitbakeAnalytics_ELC_Portland.pdf)		** Use a Python script to find and dump desired database records (see http://events.linuxfoundation.org/sites/events/files/slides/BitbakeAnalytics_ELC_Portland.pdf)

			=== Specific error scenarios ... ===

			* The build progress gets stuck at "Loading..."
			** You have a syntax error, either in 'localhostbecontroller.py', the helper classes in 'models.py', or in the related javascript. Look at the tail of "toaster_runbuilds.log" file for pythons errors, and in your browser's "Console" for javascript errors.
	* The message "Sorry, An error has occurred loading this page"		* The message "Sorry, An error has occurred loading this page"
	** The included javascript has a syntax error. The HTML page being rendered has local JS code at the top that caches these errors and displays the observed message (in order to be less ugly to the customer). That code also tries to add the error message to the browser console but that does not always work, and you are left with no clue		** The included javascript has a syntax error. The HTML page being rendered has local JS code at the top that caches these errors and displays the observed message (in order to be less ugly to the customer). That code also tries to add the error message to the browser console but that does not always work, and you are left with no clue

David Reyna: /* How to debug a ... */

2018-06-20T21:35:43Z

How to debug a ...

← Older revision		Revision as of 21:35, 20 June 2018
Line 474:		Line 474:
	** Use an application like "sqlitebrowser" to examine the tables and records		** Use an application like "sqlitebrowser" to examine the tables and records
	** Use a Python script to find and dump desired database records (see http://events.linuxfoundation.org/sites/events/files/slides/BitbakeAnalytics_ELC_Portland.pdf)		** Use a Python script to find and dump desired database records (see http://events.linuxfoundation.org/sites/events/files/slides/BitbakeAnalytics_ELC_Portland.pdf)
			* The message "Sorry, An error has occurred loading this page"
			** The included javascript has a syntax error. The HTML page being rendered has local JS code at the top that caches these errors and displays the observed message (in order to be less ugly to the customer). That code also tries to add the error message to the browser console but that does not always work, and you are left with no clue
			** You can start bisecting the recent edits you made to the respective JS files to locate the problem change
			** You can also add a breakpoint in the mentioned catch code to see if you can see the error directly

	=== How to update from a fix in a ... ===		=== How to update from a fix in a ... ===

David Reyna: /* Workflow */

2018-04-20T03:01:16Z

Workflow

← Older revision		Revision as of 03:01, 20 April 2018
Line 59:		Line 59:
	10) NOTE: when the patch has been accepted upstream, you can clean up your poy-contrib branch with:		10) NOTE: when the patch has been accepted upstream, you can clean up your poy-contrib branch with:

	<code> git push -u poky-contrib :username/toaster/FeatureOrBug~~</code>~~ </code>		<code> git push -u poky-contrib :username/toaster/FeatureOrBug </code>

	=== Sending patches to Toaster Project ===		=== Sending patches to Toaster Project ===