CPs: ci.yaml changes for packaging #117196
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* 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 <[email protected]>
This is removing the temporary comments and simplifying the name. Bug: #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: #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. |
fluttergithubbot
approved these changes
Dec 16, 2022
XilaiZhang
approved these changes
Dec 16, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.