Follow up from #165258 Removes references to the deleted Infra-Ticket-Queue.md, and mentions of the Infra Ticket Queue Github project. Not sure if we should keep the issue template? ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [ ] I listed at least one issue that this PR fixes in the description above. - [x] I updated/added relevant documentation (doc comments with `///`). - [x] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing. If you need help, consider asking for advice on the #hackers-new channel on [Discord]. <!-- Links --> [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md
This commit is contained in:
Kate Lovett
@@ -137,7 +137,7 @@ See the [golden test build breakage] guide.
|
||||
1. Open a [new infra issue].
|
||||
1. Add a descriptive title. A message like "Add a LUCI builder for linux web engine" or "Debug gallery startup" is much more helpful than "quick request" or "test doesn't work?".
|
||||
1. Clearly describe the issue or request in the description field. For example, if a ticket is requesting running several commands on the bots, the ticket should explain why, what commands are needed, on which bots and how to verify the results.
|
||||
1. Add the `team: infra` label and a priority label:
|
||||
1. Add the `team-infra` label and a priority label:
|
||||
* `P0` (immediate): Such as a build break or regression.
|
||||
* Fix as soon as possible, before any other work.
|
||||
* Should be very rare, and only used when critical work is blocked without a workaround.
|
||||
@@ -147,8 +147,6 @@ See the [golden test build breakage] guide.
|
||||
* Degraded service (Build bots work but are slow to start).
|
||||
* Time-sensitive requests.
|
||||
* Should be relatively rare.
|
||||
* Anything below `P1` is not suitable for the infra ticket queue and will be treated as a normal infra bug.
|
||||
1. Add the project "Infra Ticket Queue".
|
||||
1. Click the create button. No need to set an assignee; infra oncall will handle all new tickets.
|
||||
|
||||
## Communication channels (public)
|
||||
|
||||
@@ -11,6 +11,5 @@ This is an index of team-facing documentation for topics relating to Engineering
|
||||
- [Flutter's Build Infrastructure](../../dev/bots/README.md)
|
||||
- [Flutter's repository architecture](../about/Flutter's-repository-architecture.md)
|
||||
- [GitHub Action Workflows](GitHub-Action-Workflows.md)
|
||||
- [Infra Ticket Queue](Infra-Ticket-Queue.md)
|
||||
- [Labeling PRs](../contributing/Labeling-PRs.md)
|
||||
- [New Android Version](../platforms/android/New-Android-version.md)
|
||||
@@ -25,7 +25,6 @@ An example build: [Linux color_filter_and_fade_perf__e2e_summary](https://ci.chr
|
||||
1. Check if the infra failure has happened on earlier builds by clicking (i)
|
||||
2. Check if issue already exists in the [infra bug pool](https://github.com/flutter/flutter/issues?q=is%3Aopen+is%3Aissue+label%3A%22team%3A+infra%22)
|
||||
3. If not, file [an infra bug](https://github.com/flutter/flutter/issues/new?template=6_infrastructure.yml)
|
||||
4. If this is a blocking failure, please add Projects [`Infra Ticket Queue`](./Infra-Ticket-Queue.md). The infra gardener will scan through the queue frequently.
|
||||
5. If you want to get an immediate help, please ask in the discord `hackers-infra` channel
|
||||
6. If this is an infra flake, and a retry is needed
|
||||
* For pre-submit test, click `Re-run` in the [check run page](https://github.com/flutter/flutter/pull/83894/checks?check_run_id=2738146673). 
|
||||
|
||||
Reference in New Issue
Block a user