Maniphest T193258

Look into ways to identify risky commits that are part of the weekly branch cut, either manually or through automated process
Open, MediumPublic
Actions

Assigned To

None

Authored By

	• mmodell
	Apr 27 2018, 5:01 PM

Description

This was identified as an action item during the postmortem review 20180229-Train-1.31.0-wmf.27.

Essentially what we discussed is that some changes are inherently risky and should be released more cautiously. The SWAT deployment process addresses this need for changes which happen throughout the week, however, some changes don't make it into a SWAT and instead they go out with the train. The weakness is due to the fact that the train deployment process does not alert key people when their patch is being deployed. So instead of having an alert developer on hand to test a patch as it's being deployed you have the situation where deployers have to track down the cause of errors and then attempt to contact developers who are knowledgeable about the changes in question. The whole process is awkward and time consuming.

Prior art:

Predicting Risk of Software Changes (PDF) by AUDRIS MOCKUS and DAVID M. WEISS
CodeGuru commit analyzer (PDF) | source ()

Related Objects
Search...

Status	Subtype	Assigned	Task
Open		None	T193258 Look into ways to identify risky commits that are part of the weekly branch cut, either manually or through automated process
Resolved	PRODUCTION ERROR	• mmodell	T190960 1.31.0-wmf.27 rolled back due to increase in fatals: "Replication wait failed: lost connection to MySQL server during query"
Open		None	T210533 Code Health Metrics should enable commit and/or patch set risk assessment

Event Timeline

• mmodell created this task.Apr 27 2018, 5:01 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 27 2018, 5:01 PM

• mmodell added a subtask: T190960: 1.31.0-wmf.27 rolled back due to increase in fatals: "Replication wait failed: lost connection to MySQL server during query".Apr 27 2018, 5:02 PM

• mmodell triaged this task as Medium priority.Apr 28 2018, 8:41 AM

• mmodell updated the task description. (Show Details)Apr 28 2018, 8:51 AM

Time to bring back scaptrap?

@Legoktm - indeed, that was mentioned in the meeting, and I think it's a good idea.

greg edited projects, added Release-Engineering-Team; removed Train Deployments.May 2 2018, 9:33 PM

Jdforrester-WMF subscribed.May 2 2018, 9:34 PM

• Vvjjkkii renamed this task from Look into ways to identify risky commits that are part of the weekly branch cut, either manually or through automated process to 12daaaaaaa.Jul 1 2018, 1:13 AM

• Vvjjkkii raised the priority of this task from Medium to High.

• Vvjjkkii added projects: CheckUser, Connected-Open-Heritage-Batch-uploads (RAÄ-KMB_1_2017-02), Tamil-Sites, Gamepress, Hashtags, Jade, KartoEditor, Language-2018-Apr-June, New-Editor-Experiences, Mail, TCB-Team (now WMDE-TechWish).

• Vvjjkkii updated the task description. (Show Details)

• Vvjjkkii removed a subscriber: Aklapper.

ArielGlenn renamed this task from 12daaaaaaa to Look into ways to identify risky commits that are part of the weekly branch cut, either manually or through automated process.Jul 1 2018, 1:23 PM

ArielGlenn lowered the priority of this task from High to Medium.