[EPIC] Code Deploy Dashboard
Open, LowPublic
Actions

Assigned To

None

Authored By

	greg
	Jul 15 2014, 12:18 AM

Description

Problem:

We don't have an simple way of communicating what code is deployed to which wikis. Right now you need a combination of Gerrit and the MediaWiki Roadmap.

Stakeholders/use-cases:

Product Managers: I want to see one page where I can tell if code my team has developed is on all Wikipedias.
Developers: I want to know when code I have written is on the test wikis and when it'll be on English Wikipedia.
Technical Users/Readers: I want to see if there's an obvious excuse for a problem I am seeing on my home wiki due to a recent deployment.
Release Team: All of the above.

Solution ideas:

Create a dashboard page, hosted in Gerrit that displays the currently deployed/active branches on the WMF Cluster (and, for bonus points, the Beta Cluster). The branches will link to a single page in Gerrit that lists all of the changes and their commit short message.
The above, but hosted on mediawiki.org (managed by a bot, on commit, so it is not out of date).
The above, but hosted on its own vhost and running on the git.wikimedia.org

Details

Reference: fl454

	Title	Reference	Author	Source Branch	Dest Branch
	GrowthExperiments: Link suggestion support	repos/ci-tools/patchdemo!305	matmarex	github/fork/kostajh/T280664	master

Customize query in GitLab

Related Objects
Search...

Status	Assigned	Task
Open	None	T280 [EPIC] Code Deploy Dashboard
Resolved	Legoktm	T100347 ForrestBot should run for WMF-deployed extensions as well as MediaWiki core
Resolved	Legoktm	T100817 Move list of extensions and skins branched in make-wmf-branch out of a PHP file
Resolved	Legoktm	T100811 Rename "Forrestbot" to "ReleaseTaggerBot"
Open	None	T100812 Have ReleaseTaggerBot automatically create new deploy branch (release) projects
Open	None	T100814 Have ReleaseTaggerBot also tag versioned libraries we control
Declined	• mmodell	T101128 Create a phabricator application that simply summarizes which branches are currently deployed, in an easily understandable format.

Event Timeline

greg wrote on 2014-07-15 00:19:22 (UTC)

20:14 < Ryan_Lane> greg-g: for the code deploy dashboard...
20:14 < Ryan_Lane> trebuchet writes its deployment info into redis
20:14 < Ryan_Lane> if we change its schema some we can track each deployment separately by tag
20:15 < Ryan_Lane> as well as the deployment message that went along with it
20:15 < Ryan_Lane> then a dashboard could just read from redis
20:16 < Ryan_Lane> currently each deployment for a repo overwrites the data from the last, to make things simpler
20:16 < Ryan_Lane> hm. or does it? did I change that
20:16 < Ryan_Lane> I need to document the schema being used
20:17 < Ryan_Lane> hm, I should also put the schema/attribute mapping in a pillar so that it can be changed without needing to modify the code everywhere later, in a different channel
00:18 < Ryan_Lane> it [NB: a dashboard] was my original intention for the data, but a cli was quicker/easier to build

• flimport added a subscriber: greg.Oct 2 2014, 9:58 PM

• mmodell subscribed.Oct 21 2014, 4:48 PM

Another suggested solution: integrate this into phabricator as a phab dashboard panel?

greg lowered the priority of this task from Low to Lowest.Jan 8 2015, 6:00 PM

greg moved this task from To Triage to Backlog (Tech) on the Deployments board.

greg mentioned this in T88136: Indicate deployed status (wmf branch) for Gerrit patches in Phabricator.Jan 30 2015, 7:17 PM

Legoktm added a project: Wikimedia-Hackathon-2015.Feb 25 2015, 7:45 PM

Legoktm set Security to None.

Qgil moved this task from Backlog to Hacking proposals on the Wikimedia-Hackathon-2015 board.Feb 27 2015, 10:41 AM

greg mentioned this in T92565: Release/QA tasks at the Wikimedia Hackathon 2015.Mar 12 2015, 9:16 PM

Florian subscribed.Mar 12 2015, 9:28 PM

Quiddity awarded a token.May 15 2015, 6:23 AM

Glaisher subscribed.May 24 2015, 3:56 AM

We have gone for the 'assign tags to bugs' approach instead, allowing users to search for changes within Phabricator. It's not really a /dashboard/ per se, but it does the job of communicating 'this change will be in release X'.

Hackish but working code at http://github.com/valhallasw/forrestbot, @Legoktm has relevant credentials.

valhallasw mentioned this in T96378: Wikimedia Hackathon 2015 showcase.May 25 2015, 10:28 AM

Seems to me the requirements are fulfilled by @Forrestbot

It spams tag to tasks somehow https://phabricator.wikimedia.org/p/Forrestbot/feed/

An example is T100248 which has the Phabricator tags:

MW-1.26-release
WMF-deploy-2015-05-13_(1.26wmf6)
WMF-deploy-2015-05-20_(1.26wmf7)
WMF-deploy-2015-05-27_(1.26wmf8)

Example addition:

In T100248#1311606, @Forrestbot wrote:

https://gerrit.wikimedia.org/r/213602 (branch master): MW-1.26-release, WMF-deploy-2015-05-27_(1.26wmf8)

I am bringing this to Release-Engineering-Team team meeting on 2015-06-02.

hashar moved this task from INBOX to In-progress on the Release-Engineering-Team board.May 29 2015, 10:29 AM

Legoktm assigned this task to • Forrestbot.May 29 2015, 5:53 PM

Legoktm added a project: ReleaseTaggerBot.

Jdforrester-WMF added a subtask: T100347: ForrestBot should run for WMF-deployed extensions as well as MediaWiki core.May 29 2015, 6:03 PM

Jdforrester-WMF raised the priority of this task from Lowest to Medium.May 29 2015, 6:09 PM

I have removed Release-Engineering-Team from all the subtask since they are already in Deployments. We attempt to only get the root task / Epic on our board hence the cleanup.

Did anyone work on this task at Wikimedia-Hackathon-2015? If so, please share an update. If not, remove the label.

In T280#1324933, @Qgil wrote:

Did anyone work on this task at Wikimedia-Hackathon-2015? If so, please share an update. If not, remove the label.

Updates were shared two comments above: T280#1307224 and T280#1320202.

Qgil moved this task from Hacking proposals to Work continues after Lyon on the Wikimedia-Hackathon-2015 board.Jun 1 2015, 7:23 AM

I would like to build a phabricator application that summarizes this information in a nice and easily parsable way, in a single canonical location.

I don't think forrestbot completely satisfies the need for a summary of this information, rather, the information is scattered about in various phabricator objects.

greg removed • Forrestbot as the assignee of this task.Jun 3 2015, 10:18 PM

We are trying to help all open tasks listed under "Work continues after Lyon" at the Wikimedia Hackathon 2015 workboard finding their best way forward. * If you are participating in Wikimania, consider adding the #Wikimania-Hackathon-2015 project to get this task in that loop, which is about to start. * If you think this project could welcome help from a dedicated Google Summer of Code or Outreachy intern, or from an Individual Engagement Grant, add the Possible-Tech-Projects project. * If you would like to receive some other type of support (organizing a Tech Talk, establishing contacts with existing developer teams in Wikimedia or elsewhere, travel sponsorship for a related activity... you name it), please create a subtask explaining your request and associate it with #Engineering-Community (or you can start by commenting here if you prefer). * Keeping the description, priority and assigned fields up to date always helps. :) For some context about this message, see T101151: Evaluate which projects showcased at the Wikimedia Hackathon should be supported further. It is the last communication related to Wikimedia-Hackathon-2015 that we will post here.