-
Notifications
You must be signed in to change notification settings - Fork 26.8k
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.
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
CPs: ci.yaml changes for packaging #117196
CPs: ci.yaml changes for packaging #117196
Conversation
* packaging builder initial config * add release scheduler parameter * remove stables * add taskname + test owner * testowner test * comment structure * test naming convention * test adding tags * add timeout * prune names * Update testowners. * Move packaging to shards section. * Set packaging as shard. * Use packaging V2 Co-authored-by: godofredoc <godofredoc@google.com>
This is removing the temporary comments and simplifying the name. Bug: flutter#115489
* add stable packaging builders * update testowners * consolidate and use enabled_branches * update to reflect the consolidation
It includes the following changes: * Adds main as the enabled branches. * Adds docs_beta and docs_stable to pass the expected gcp project. * Adds dimensions to packaging arm64 to ensure that it runs on arm64 bot. Bug: https://github.com/orgs/flutter/projects/43
* Pass drone_dimensions as part of the main target. Drone dimensions were passed as properties when the sharding utility is expecting them in the target. Bug: flutter#116794 * Use dimensions instead of drone_dimensions. * Use a map format.
It includes the following changes: * Adds main as the enabled branches. * Adds docs_beta and docs_stable to pass the expected gcp project. * Adds dimensions to packaging arm64 to ensure that it runs on arm64 bot. Bug: https://github.com/orgs/flutter/projects/43
Without passing this dimension there is a chance that the build will run on a arm64 machine.
This pull request was opened from and to a release candidate branch. This should only be done as part of the official Flutter release process. If you are attempting to make a regular contribution to the Flutter project, please close this PR and follow the instructions at Tree Hygiene for detailed instructions on contributing to Flutter. Reviewers: Use caution before merging pull requests to release branches. Ensure the proper procedure has been followed. |
CP: 30fc993
CP: 1b05653
CP: e07240e
CP: e52449b
CP: 1da8f4e
CP: bd0791b
CP: 1da8f4e
CP: a41c447
Pre-launch Checklist
///
).If you need help, consider asking for advice on the #hackers-new channel on Discord.