Skip to content

add build rotation doc #42005

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Sep 10, 2020
Merged

add build rotation doc #42005

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
f71d2c1
add build rotation doc
Anipik Sep 9, 2020
1130725
Update docs/buildtriage.md
danmoseley Sep 9, 2020
fa0f428
address feedback
Anipik Sep 9, 2020
8ae01b3
removing the extra table
Anipik Sep 9, 2020
f121f82
Update docs/buildtriage.md
Anipik Sep 10, 2020
a5c80bf
remove pass rate
Anipik Sep 10, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
39 changes: 39 additions & 0 deletions docs/buildtriage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@
## Build Triage Rotation

The responsibility of this role is triaging our rolling / official builds, filing issues to track broken tests, submitting changes to dotnet/runtime to work around issues (disabling a test, undoing a PR that broke the build).

In some cases this will require working with core-eng team when the issues are in Helix / Azure / Arcade. This person will also attend CI Council with the infra manager to provide updates on our reliability status.

This directly impacts developer productivity and the need to promptly fix such breaks can span across time zones. Hence it will be the collective responsibility of the Scout pool to investigate such breaks.

This role will work on a rotation basis. There are six people in the role and each rotation will last for a calendar month.

## Tracking Build Failures
All the CI failures can be tracked through the CI Council dashboards i.e. [Public](https://dev.azure.com/dnceng/public/_dashboards/dashboard/40ac4990-3498-4b3a-85dd-2ffde961d672), [Internal](https://dev.azure.com/dnceng/internal/_dashboards/dashboard/e1bb572d-a2b0-488f-a58a-54c73a547f0d).
We have different dashboards for public(Rolling & PR Builds) and internal builds.

Tests are not run during the internal builds. Publishing and signing steps are run only during internal builds. Rolling builds run tests for the full matrix.

Contact @chcosta if you are having any trouble accessing the dashboards.
Contact @Chrisboh if you don't have the calendar invite for the CI Council meeting.

## Ongoing Issues

All the issues causing the builds to fail should be marked with [`blocking-clean-ci`](https://github.com/dotnet/runtime/issues?q=is%3Aissue+is%3Aopen+label%3Ablocking-clean-ci) label.
Any issues causing build breaks in the official build should be marked with [`blocking-clean-official`](https://github.com/dotnet/runtime/issues?q=is%3Aissue+is%3Aopen+label%3Ablocking-clean-official).
It helps in tracking issues effectively.

## Some helpful resources
- [runfo Website](https://runfo.azurewebsites.net/)
- [runfo Documentation](https://github.com/jaredpar/devops-util/tree/master/runfo)
- [Internal Build Definition](https://dev.azure.com/dnceng/internal/_build?definitionId=679)
- [Public Build Definition](https://dev.azure.com/dnceng/public/_build?definitionId=686)

## Build Rotation for upcoming months

| Month | Alias |
|-------|-----------|
| September | @directhex |
| October | @jkoritzinsky |
| November | @aik-jahoda |
| December | @akoeplinger |