-
Notifications
You must be signed in to change notification settings - Fork 7.8k
Split CI testing based on flutter channels #651
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
Split CI testing based on flutter channels #651
Conversation
…le-beta-dev-ci-split
…le-beta-dev-ci-split
PTAL @redbrogdon 😄 |
…le-beta-dev-ci-split
…le-beta-dev-ci-split
@domesticmouse, this is great. I love that it'll get some of the experimental samples under test with the correct branches. We had two PRs relating to CI setup in flight at the same time, and the other one has been landed. Mind doing a rebase and double-checking that everything is still how you want it? |
|
||
defaults: | ||
run: | ||
shell: bash |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting. Is it running zsh on macOS?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or PowerShell on Windows? 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Powershell on windows by default was the issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Holy cow. I was just kidding around. 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
heh, holy cow is usual state of play for DevOps =)
Split out the CI testing between
stable
,beta
, anddev
. This enables us to specify which samples are tested on which specific channel(s).Note, the prior Github Actions CI configuration was masking various breaks, both on untested beta and dev targeted samples, and on the Android compilation CI. I've raised tracking bugs for the various breakages.