mirror of
https://github.com/flutter/flutter.git
synced 2025-06-03 00:51:18 +00:00

3 notable places I did not migrate. 1. engine/src/flutter/docs/Engine-disk-footprint.md treemaps and what hash is used for what upload. 1. engine/src/flutter/lib/gpu/pubspec.yaml, I didnt want this pr to update code that could need to be reverted and I didnt know what to do to test that publishing would not break or cause a downstream breakage. 1. engine/src/flutter/build/zip_bundle.gni I wasnt sure how to test my changes. Reviewers: Please let me know if you want a different link or if you would prefer something unmodified. Commits: - **Replace triage links with equivalents, change pull request to generic flutter/flutter, replace code search link with equivalent** - **Change link from flutter/engine to engine folder, modify link text to team** - **replace engine repo link with engine folder, replace text repo with folder** - **replace engine specific security info with flutter generic** - **replace engine roller comment with a skia roller equivalent** - **link to same file in new location** - **Remove comment that some code lives in flutter/flutter and some in flutter/engine** - **Say to bump dart in flutter/flutter without mentioning engine** - **Replace documentation with new locations** - **replace code printed comments with new locations** Partially addresses https://github.com/flutter/flutter/issues/167478 ## 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]. - [x] 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.
8.9 KiB
8.9 KiB
Flutter Self Service Index
Flutter provides multiple functionality through self-service services. Most of these services are available to any member of the Flutter GitHub organization.
Audiences
Name | Description |
Flutter contributors | Anyone contributing to the flutter organization independently of membership to the organization. |
Flutter organization members | [Anyone with write access to the flutter organization resources.](./contributing/Contributor-access.md) |
Googlers | Members of the Flutter Organization that are also Googlers. |
Flutter organization administrators | Members of the Flutter organization that have write access to the organization's settings. |
Infrastructure
Service | Description | Audience | Documentation | Location |
.ci.yaml | Configuration file to instruct the Flutter Infrastructure which tasks to use to validate commits in a given repository. ".ci.yaml" is read from the top level folder of every supported repository. | Flutter contributors | Link | Top level folder of the GitHub repositories. E.g. flutter/flutter. |
Engine build configurations | Configuration files to describe Flutter Engine builds and tests. | Flutter contributors | Link | engine/src/flutter/ci/builders in the flutter engine folder contains all the current configuration files. |
Autosubmit | GitHub application that auto-submits pull requests that meet the approval criteria. | Flutter organization administrators | Link | The application code is available in the flutter/cocoon repository. |
FirebaseLab tests | Special type of tests configured through .ci.yaml that use resources from FirebaseLab | Flutter contributors | [Link](./infra/Flutter-FirebaseLab-Tests.md) | These configurations go directly in the .ci.yaml file of flutter/flutter repository. |
Codesigning | Add metadata to engine artifacts for code signing infrastructure to sign them. | Flutter contributors | [Link](./engine/release/Code-signing-metadata.md) | GN files and global generator scripts in the flutter engine folder. |
Emulators support | Using android emulators from tests. | Flutter contributors | [Link](./platforms/android/Testing-Android-Changes-in-the-Devicelab-on-an-Emulator.md) | Flutter GitHub Wiki page under the “Android Development” Section. |
Rerun GitHub presubmit test using command line | Run presubmit tasks using `reset-try-task` end point and gcloud CLI. | Googlers | Link | Source code is available here |
Rerun postsubmit test from Flutter build dashboard | Re-run postsubmit tasks from the go/flutter-dashboard. | Googlers | Link | Source code is available go/flutter-dashboard |
Run a test multiple times in parallel via LED | Run a shard test against a pull request to validate changes/fixes in parallel. | Googlers | Link | N/A |
Create a CIPD package | Create and add the package build scripts to cocoon to enable auto building and uploading to flutter CIPD namespaces. | Flutter contributors | Link | Flutter public CIPD namespace: flutter |
View Infra SLO metrics | DataSite with links to a collection of Engineering Productivity dashboards including infrastructure, release and rolls. | Googlers | Link | N/A |
Release
Service | Description | Audience | Documentation | Location |
Create non flutter release candidate branches | Self service to create release candidate branches used by products different than flutter | Googlers | Link | N/A |
Request 1P cherry picks | Request approvals for cherry picks to release candidate branches | Googlers | Link | flutter/flutter |
G3 Fixes | Apply G3 fixes that are automatically applied during the roll process. | Googlers | Link | N/A |
Single command releases | Creating a third party flutter release with multi party approvals. | Release Engineering | Link | N/A |
Security
Service | Description | Audience | Documentation | Location |
Vulnerability scanning and fixes validation | Automatic scanning of c, c++ third party dependencies and vulnerability. fix validation. | Flutter organization members | Link | Flutter GitHub security tab. |
Request write access to non-prod GCP projects | Googlers | Link | N/A | |
Rolling non-auto-updating 3p mirrored deps | Dependencies on mirrors that do not automatically roll changes from their upstream might need to be manually rolled | Googlers | Link | N/A |
Googlers can access the internal version using go/flutter-self-service