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
ci: skip windows e2e tests in specific scenario #2386
Conversation
57503fe
to
d8461c7
Compare
09f4195
to
7d31fad
Compare
7d31fad
to
7785f6a
Compare
As discussed with @TMisiukiewicz this Pull Request needs to be first merged to work correctly - Windows shouldn't be triggered when there's only change in |
@@ -17,3 +17,4 @@ export {default as installPods} from './tools/installPods'; | |||
|
|||
export {default as findXcodeProject} from './config/findXcodeProject'; | |||
export {default as findPbxprojFile} from './config/findPbxprojFile'; | |||
console.log('hello'); |
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.
Leftover
with: | ||
list-files: shell | ||
filters: | | ||
specific_dir: |
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.
Let’s rename this to something like „apple_dirs” in a follow-up PR and adjust the name of the job. „Changes” is super ambiguous.
Summary:
When there's a change only in
cli-platform-apple
orcli-platform-ios
it doesn't make sense to triger also Windows jobs, because there's no scenario that change in these packages would broke Windows builds.Test Plan:
If there's only a change in
cli-platform-apple
orcli-platform-ios
Windows jobs shouldn't be triggered.Checklist