-
Notifications
You must be signed in to change notification settings - Fork 6.8k
build: share release output between circle jobs #13838
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
build: share release output between circle jobs #13838
Conversation
ef7bb68
to
be3e022
Compare
be3e022
to
9696ff8
Compare
c95e4ed
to
766b23a
Compare
const chunkSize = Math.floor((browsers.length - assignedBrowsers) / (maxInstances - i)); | ||
chunks[i] = browsers.slice(assignedBrowsers, assignedBrowsers + chunkSize); | ||
assignedBrowsers += chunkSize; | ||
} |
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.
@jelbourn You probably have some better ideas to split an array into a maximum size of chunks in a deterministic way.
Note that I intentionally didn't consider splitting the actual tests across browsers because we want to run all specs on all browsers specified for BrowserStack
.
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.
LGTM
That array splitting is fine
Also support parallel Karma instances on CircleCI
Also support parallel Karma instances on CircleCI
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Runs a new job that builds the release output and persists it to the CircleCI workspace storage. This can be used to run the AOT tests, CLI integration tests (#13456), publish artifacts etc without rebuilding everything again.
Runs two parallel instances of Browserstack with the goal of replacing Saucelabs completely with Browserstack. Also a benefit is that we can now use packages like
karma-parallel
to speed up tests per instance without the downside of just running specific tests on a specific browser.