Build Champion

This role is inspired by the role in the vscode repo. This page is primarily a copy of vscode's Build Champion wiki page, edited to be relevant to vscode-jupyter.

Responsibilities

• Daily: Triage all failed builds
• On the following Monday: Hand over the role to the next person

This page describes the Build Champion role. This is a weekly rotating role within the team.

Triage non-green builds

👉 The main role of the build champ is to ensure our build remains trusted by driving down flakiness and to reduce team randomization.

At least once per day, the build champ should review the builds for commits going into the main branch, and investigate any that didn't pass.

Test failure: If it looks like the test failed because of the linked change, ping the committer. If it looks like the test flaked, you can search for issues with the "flaky test" label to find an existing issue and comment on it, or open a new one. You can skip the test if it flakes multiple times, or skip it immediately.

Compile failure: If this was a recent failure and the "Changes" seems relevant, ping the committer if they have not yet commented.

Address un-triaged marketplace reviews

1. For bugs or feature suggestions, create an issue on vscode-jupyter, and add appropriate tag(s).
2. In the details, indicate that the issue is from marketplace review, and paste the review contents as a quote in the details. See example here.
3. If able, cc the author of the review on the GH issue.
4. Link the GH issue back to the marketplace review as a part of the response. Here is an example response:

Hello! We're sorry to hear about this issue, and thank you for contacting us! We've created a GitHub issue for further discussion and troubleshooting:

https://github.com/microsoft/vscode-jupyter/issues/<issue-number>

We'll be able to get to the bottom of this better if you can provide logs and environment data. We hope to connect with you there and help!

Note: If you do not have access to respond to the review, post on the team Slack channel to be added as an Owner on the publisher page.

Appendix

Area owners

If you're unsure who owns an area, you can check the ownership file or git history.

Useful links

• GH Actions builds in main
• Dealing with test flakiness wiki page