User:Joshua Lock/SWAT - Revision history

Joshua Lock: Name more people and mention more bug categories

2016-11-15T16:10:13Z

Name more people and mention more bug categories

← Older revision		Revision as of 16:10, 15 November 2016
Line 22:		Line 22:
	'''Active member''': the currently active member of the SWAT team is expected to monitor the Autobuilder and pre-triage failures in a timely fashion. Team members are active for one week at a time.		'''Active member''': the currently active member of the SWAT team is expected to monitor the Autobuilder and pre-triage failures in a timely fashion. Team members are active for one week at a time.

	'''SWAT Chair''': the SWAT chair provides backup cover for the active member and is a first point of contact for SWAT.		'''SWAT Chair''': the SWAT chair provides backup cover for the active member and is a first point of contact for SWAT. [[User:Tracy_Graydon\| Tracy Graydon]] is the current SWAT Chair.

	'''SWAT Facilitator''': the SWAT facilitator is responsible for managing the rotation process.		'''SWAT Facilitator''': the SWAT facilitator is responsible for managing the rotation process. [[User:Stephen_K._Jolley\| Stephen Jolley]] is the current SWAT Facilitator.

	== Process ==		== Process ==
Line 37:		Line 37:
	** When it isn't obvious which patch caused the failure file an issue in bugzilla and alert the branch owner (CC or assignment on the bug should suffice).		** When it isn't obvious which patch caused the failure file an issue in bugzilla and alert the branch owner (CC or assignment on the bug should suffice).
	** '''If in doubt file a bug''', ''all'' observed errors must be actioned unless a patch has already been sent for the issue (in which case please make note of this in the [[BuildLog]]).		** '''If in doubt file a bug''', ''all'' observed errors must be actioned unless a patch has already been sent for the issue (in which case please make note of this in the [[BuildLog]]).
			** Infrastructure issues can be filed in bugzilla, where they will be assigned to [[User:Halstead\| Michael Halstead]] (''halstead'' on irc) by default.
			** Autobuilder logic bugs also go into bugzilla, where they will be assigned to [[User:Joshua_Lock\| Joshua Lock]] by default.

	The results of pre-triage for an issue should be added to the corresponding entry in the [[BuildLog]], including a link to the pre-triage outcome (bugzilla entry, mailing list post in the archive, etc) and a brief summary of the issue.		The results of pre-triage for an issue should be added to the corresponding entry in the [[BuildLog]], including a link to the pre-triage outcome (bugzilla entry, mailing list post in the archive, etc) and a brief summary of the issue.
Line 65:		Line 67:
	** File a bugzilla ticket ''OR'' respond to a patch ''OR'' note known issues		** File a bugzilla ticket ''OR'' respond to a patch ''OR'' note known issues
	** Update the [[BuildLog]] with the result of pre-triage, linking to issues/mail archives when possible		** Update the [[BuildLog]] with the result of pre-triage, linking to issues/mail archives when possible

			== Questions / Contact ==



	== Members ==		== Members ==
Line 75:		Line 81:
	* Juro Bystricky (US)		* Juro Bystricky (US)
	* Anibal Limon (MX)		* Anibal Limon (MX)
	* Tracy Graydon (US) (SWAT Chair)		* [[User:Tracy_Graydon\| Tracy Graydon]] (US) (SWAT Chair)
	* Alejandro Hernandez (MX)		* Alejandro Hernandez (MX)
	* Jussi Kukkonen (FI)		* Jussi Kukkonen (FI)

Joshua Lock: /* Process summary */

2016-11-15T15:26:58Z

Process summary

← Older revision		Revision as of 15:26, 15 November 2016
Line 64:		Line 64:
	* Pre-triage each failure:		* Pre-triage each failure:
	** File a bugzilla ticket ''OR'' respond to a patch ''OR'' note known issues		** File a bugzilla ticket ''OR'' respond to a patch ''OR'' note known issues
	** Update the [[BuildLog]] with the result of pre-triage, linking to issues/mail ~~archived~~ when possible		** Update the [[BuildLog]] with the result of pre-triage, linking to issues/mail archives when possible

	== Members ==		== Members ==

Joshua Lock: /* Members */

2016-11-15T15:25:53Z

Members

← Older revision		Revision as of 15:25, 15 November 2016
Line 68:		Line 68:
	== Members ==		== Members ==

	* Saul Wold (US~~) (Autobuilder Administrator~~)		* Saul Wold (US)
	* Paul Eggleton (NZ)		* Paul Eggleton (NZ)
	* Ross Burton (UK)		* Ross Burton (UK)

Joshua Lock: /* Process */ mention where the "Reason" comes from

2016-11-11T11:42:37Z

Process: mention where the "Reason" comes from

← Older revision		Revision as of 11:42, 11 November 2016
Line 28:		Line 28:
	== Process ==		== Process ==

	The [[BuildLog]] wiki page is automatically updated by the autobuilder when a new build is triggered. An entry should include a reason for triggering the build and may also include detail on what the expectations for the build are.		The [[BuildLog]] wiki page is automatically updated by the autobuilder when a new build is triggered. An entry should include a reason for triggering the build (as entered in the "Reason" field of the autobuilder "Force build" page when triggering a build) and may also include detail on what the expectations for the build are.
	For each build failure that occurs the active SWAT member is responsible for pre-triaging the failure.		For each build failure that occurs the active SWAT member is responsible for pre-triaging the failure.

Joshua Lock: /* Process */ punctuation

2016-11-11T11:38:09Z

Process: punctuation

← Older revision		Revision as of 11:38, 11 November 2016
Line 34:		Line 34:

	* for builds against a master or release branch of the poky repo any issues observed should be [[#Filing_bugs \| filed in bugzilla]].		* for builds against a master or release branch of the poky repo any issues observed should be [[#Filing_bugs \| filed in bugzilla]].
	* for builds against other branches (master-next, ross/mut, -next branches for stable releases, etc.) where an issue is caused by a patch not in the master branch the relevant unmerged patch causing the problem should be replied to on the mailing list.		* for builds against other branches (master-next, ross/mut, -next branches for stable releases, etc.), where an issue is caused by a patch not in the master branch, the relevant unmerged patch causing the problem should be replied to on the mailing list.
	** When it isn't obvious which patch caused the failure file an issue in bugzilla and alert the branch owner (CC or assignment on the bug should suffice).		** When it isn't obvious which patch caused the failure file an issue in bugzilla and alert the branch owner (CC or assignment on the bug should suffice).
	** '''If in doubt file a bug''', ''all'' observed errors must be actioned unless a patch has already been sent for the issue (in which case please make note of this in the [[BuildLog]]).		** '''If in doubt file a bug''', ''all'' observed errors must be actioned unless a patch has already been sent for the issue (in which case please make note of this in the [[BuildLog]]).

Joshua Lock: /* Process */ suggestions from Ross

2016-11-11T11:37:34Z

Process: suggestions from Ross

← Older revision		Revision as of 11:37, 11 November 2016
Line 34:		Line 34:

	* for builds against a master or release branch of the poky repo any issues observed should be [[#Filing_bugs \| filed in bugzilla]].		* for builds against a master or release branch of the poky repo any issues observed should be [[#Filing_bugs \| filed in bugzilla]].
	* for builds against other branches (master-next, ross/mut, -next branches for stable releases, etc.) the relevant unmerged patch causing the problem should be replied to on the mailing list.		* for builds against other branches (master-next, ross/mut, -next branches for stable releases, etc.) where an issue is caused by a patch not in the master branch the relevant unmerged patch causing the problem should be replied to on the mailing list.
	** When it isn't obvious which patch caused the failure file an issue in bugzilla and alert the branch owner (CC or assignment on the bug should suffice).		** When it isn't obvious which patch caused the failure file an issue in bugzilla and alert the branch owner (CC or assignment on the bug should suffice).
	** '''If in doubt file a bug''', ''all'' observed errors must be actioned unless a patch has already been sent for the issue (in which case please make note of this in the [[BuildLog]]).		** '''If in doubt file a bug''', ''all'' observed errors must be actioned unless a patch has already been sent for the issue (in which case please make note of this in the [[BuildLog]]).
Line 46:		Line 46:
	When filing the bug, please:		When filing the bug, please:
	* cut and paste the relevant error in the bug comment, and include the log file as an attachment		* cut and paste the relevant error in the bug comment, and include the log file as an attachment
	* include the log from the ''CreateAutoConf'' step (this ensures the assignee and triage team can quickly asses this issue)		* include the log from the ''CreateAutoConf'' step as an attachment (this ensures the assignee and triage team can quickly asses this issue)
	* include a pointer to the [https://errors.yoctoproject.org ErrorLog] page associated with the failure (as ErrorLog)		* include a pointer to the [https://errors.yoctoproject.org ErrorLog] page associated with the failure (as ErrorLog)

Joshua Lock: /* Members */ name SWAT facilitator

2016-11-07T22:37:40Z

Members: name SWAT facilitator

← Older revision		Revision as of 22:37, 7 November 2016
Line 75:		Line 75:
	* Juro Bystricky (US)		* Juro Bystricky (US)
	* Anibal Limon (MX)		* Anibal Limon (MX)
	* Tracy Graydon (US)		* Tracy Graydon (US) (SWAT Chair)
	* Alejandro Hernandez (MX)		* Alejandro Hernandez (MX)
	* Jussi Kukkonen (FI)		* Jussi Kukkonen (FI)

Joshua Lock: /* Rotation Process */ update roles

2016-11-07T22:36:59Z

Rotation Process: update roles

← Older revision		Revision as of 22:36, 7 November 2016
Line 22:		Line 22:
	'''Active member''': the currently active member of the SWAT team is expected to monitor the Autobuilder and pre-triage failures in a timely fashion. Team members are active for one week at a time.		'''Active member''': the currently active member of the SWAT team is expected to monitor the Autobuilder and pre-triage failures in a timely fashion. Team members are active for one week at a time.

	'''SWAT Chair''': the SWAT chair ~~is responsible for managing the rotation process, providing~~ backup cover for the active member and as a first point of contact for SWAT.		'''SWAT Chair''': the SWAT chair provides backup cover for the active member and is a first point of contact for SWAT.

			'''SWAT Facilitator''': the SWAT facilitator is responsible for managing the rotation process.

	== Process ==		== Process ==

Joshua Lock: First draft of my understanding of current SWAT process

2016-10-21T13:45:41Z

First draft of my understanding of current SWAT process

New page

{| style="color:black; background-color:#b8ddff" width="100%" cellpadding="10" class="wikitable"
|'''Note''': The SWAT process has changed. Please read the new process information (up to, and including, section 6). If you're already au-fait with the new process you may want the [[#Process_summary|summary bullets]].
|}

== Overview ==

The role of the SWAT team is to monitor the autobuilder and investigate all failures to ensure they are logged and brought to the attention of a suitable owner.

== Scope ==

All builds run on the public autobuilder are important for the Yocto Project, whether they be a post-merge validation run (for master or a release branch) or a pre-merge test build (for master-next, ross/mut and others). Any build should be monitored by the SWAT team unless the [[BuildLog]] entry for that build indicates otherwise. That is; SWAT is opt-out by whomever triggers a build on the Autobuilder, not opt-in.

== Pre-triage ==

SWAT isn't responsible for resolving issues encountered on the Autobuilder. Their focus is on performing minimal analysis of a failure in order to ensure that it is logged and brought to the attention of a suitable owner, a process we'll refer to as pre-triage.

== Rotation Process ==

The active member rotation takes place weekly at the end of Friday. Usually, this will take a simple round robin order through the members list. In case the next person cannot take the role due to tight schedule, vacation or some other reasons, the role will be passed to the next person.

=== Roles ===
'''Active member''': the currently active member of the SWAT team is expected to monitor the Autobuilder and pre-triage failures in a timely fashion. Team members are active for one week at a time.

'''SWAT Chair''': the SWAT chair is responsible for managing the rotation process, providing backup cover for the active member and as a first point of contact for SWAT.

== Process ==

The [[BuildLog]] wiki page is automatically updated by the autobuilder when a new build is triggered. An entry should include a reason for triggering the build and may also include detail on what the expectations for the build are.
For each build failure that occurs the active SWAT member is responsible for pre-triaging the failure.

The pre-triage of failures takes two forms:

* for builds against a master or release branch of the poky repo any issues observed should be [[#Filing_bugs | filed in bugzilla]].
* for builds against other branches (master-next, ross/mut, -next branches for stable releases, etc.) the relevant unmerged patch causing the problem should be replied to on the mailing list.
** When it isn't obvious which patch caused the failure file an issue in bugzilla and alert the branch owner (CC or assignment on the bug should suffice).
** '''If in doubt file a bug''', ''all'' observed errors must be actioned unless a patch has already been sent for the issue (in which case please make note of this in the [[BuildLog]]).

The results of pre-triage for an issue should be added to the corresponding entry in the [[BuildLog]], including a link to the pre-triage outcome (bugzilla entry, mailing list post in the archive, etc) and a brief summary of the issue.

Every build failure should be addressed in the [[BuildLog]]. If it is a known issue, an entry with a single line containing "Known Issue" is sufficient (a link to further detail is, of course, much better). This assures others that the failure has been looked at and is being worked on.

=== Filing bugs ===

When filing the bug, please:
* cut and paste the relevant error in the bug comment, and include the log file as an attachment
* include the log from the ''CreateAutoConf'' step (this ensures the assignee and triage team can quickly asses this issue)
* include a pointer to the [https://errors.yoctoproject.org ErrorLog] page associated with the failure (as ErrorLog)

{| style="color:black; background-color:#b8ddff" width="100%" cellpadding="10" class="wikitable"
|'''Note''': Autobuilder logs are non-persistent, feel free to include a link to the log in a bug report but be sure to ''also'' attach a copy of the log and include relevant sections copy/pasted into the bug.
|}
{| style="color:black; background-color:#b8ddff" width="100%" cellpadding="10" class="wikitable"
|'''Note''': Sometimes, failures occur on autobuilders on private company networks. Do not post links into the bugzilla for these failures as nobody else can access them.
|}

=== Process summary ===

* Monitor builds via one (or more) of:
** the autobuilder [https://autobuilder.yoctoproject.org/main/tgrid tgrid], [https://autobuilder.yoctoproject.org/main/grid grid], [https://autobuilder.yoctoproject.org/main/waterfall waterfall]
** the [[BuildLog]] wiki page
** the [https://lists.yoctoproject.org/listinfo/yocto-builds yocto-builds] mailing list
* Pre-triage each failure:
** File a bugzilla ticket ''OR'' respond to a patch ''OR'' note known issues
** Update the [[BuildLog]] with the result of pre-triage, linking to issues/mail archived when possible

== Members ==

* Saul Wold (US) (Autobuilder Administrator)
* Paul Eggleton (NZ)
* Ross Burton (UK)
* Randy Witt (US)
* Leo Sandoval (MX)
* Juro Bystricky (US)
* Anibal Limon (MX)
* Tracy Graydon (US)
* Alejandro Hernandez (MX)
* Jussi Kukkonen (FI)
* Maxin John (FI)
* [[User:Joshua_Lock| Joshua Lock]] (UK) (Autobuilder Maintainer)
* Armin Kuster (US)