Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #11331 (closed)

Opened 7 years ago

Closed 5 years ago

Automated assistance for standup agenda preparation

Reported by: mtbcarroll Owned by: mtbcarroll
Priority: major Milestone: Unscheduled
Component: General Version: n.a.
Keywords: standup, github, scc Cc: bpindelski, sbesson, jburel, jamoore, cxallan, spli
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.

Description (last modified by mtbcarroll)

A fair chunk of what I do in standup preparation is quite automatable. A helper script should make my life easier by,

  1. Getting the list of failing jobs from Jenkins.
  1. Getting the list of feedback from QA2, having status "new" and no existing Trac tickets. Might be nice to sort them by submitting IP, then e-mail address. Would be nice to list them differently if they include an error or uploaded files: "File(s)", "Error", or "Comment" if neither, that kind of thing.
  1. Unrebased PRs need to be listed, but considering them rebased even if the open rebase PR isn't yet merged. Need to be able to locally mark PRs for not listing again, as most of us can't push to refs/notes/see_also/; that could also generate a file for sending to people who can (maybe shared gdoc).
  1. Checking the pulls dashboard for ome and openmicroscopy on GitHub, list the open PRs that are neither on hold nor excluded, but omit those that scc merge conflicts out. Need to be able to locally mark PRs for not listing again until they have changed. PRs have a "last modified" but this has to take account of further commits / force-pushes and change of label on corresponding issue. Would be nice to also be able to locally mark unchanged PRs for re-listing after a certain date.
  1. Pushing the list of above items for the standup agenda to a separate small gdoc from which I can copy and paste.

Change History (11)

comment:1 Changed 7 years ago by mtbcarroll

  • Description modified (diff)

comment:2 Changed 7 years ago by mtbcarroll

  • Description modified (diff)
  • Priority changed from minor to major
  • Summary changed from Make standup agenda preparation easier using GitHub API to Automated assistance for standup agenda preparation

comment:3 Changed 7 years ago by bpindelski

Might not give us everything we want yet, but it's still worth following this project - http://code.google.com/p/googlecl/.

comment:4 Changed 7 years ago by mtbcarroll

Unrebased PRs are at least now easier after sbesson's work on the SCC unrebased PRs Jenkins job. There are other questions about how stand-up could be done: for instance, should opening a PR create a card on Trello? Or, perhaps, reviewers/fixers can be arranged through GitHub's notion of assignees? So, there is broader context around this ticket.

comment:5 Changed 7 years ago by jamoore

  • Cc cxallan added

This is certainly something that could be discussed next week with Chris under the heading of "corgi". For example, when a PR is merged, corgi would know. Then, if we inject the logic to check def needsRebasing(self) and it returns False, we could indeed create a trello card.

comment:6 Changed 7 years ago by sbesson

Thoughts about moving this to the DevX board and breaking it into individual items via checklists/cards?

comment:7 Changed 7 years ago by jamoore

+1. (Perhaps we should involve the omego column too.)

comment:8 Changed 7 years ago by mtbcarroll

Possibly: might "scoping" include casting around for all kinds of ideas and trying to come to a consensus on what to even attempt?

comment:9 Changed 7 years ago by spli

  • Cc spli added

comment:10 Changed 6 years ago by mtbcarroll

Stand-up may move from GDocs to Trello.

comment:11 Changed 5 years ago by sbesson

  • Resolution set to invalid
  • Status changed from new to closed

With the requirement for team members to list their own PRs, closing this. We can open a RFE card if needed, but there is no need to keep it in Trac.

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.77002 sec.)

We're Hiring!