Skip to content
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(docs-infra): run cli docs examples concurrently #29103

Closed

Conversation

devversion
Copy link
Member

No description provided.

@devversion devversion force-pushed the ci/concurrent-aio-examples branch 6 times, most recently from bb80a41 to 676f721 Compare March 4, 2019 23:33
@devversion devversion added area: build & ci Related the build and CI infrastructure of the project action: review The PR is still awaiting reviews from at least one requested reviewer target: patch This PR is targeted for the next patch release labels Mar 4, 2019
@ngbot ngbot bot added this to the needsTriage milestone Mar 4, 2019
@devversion devversion marked this pull request as ready for review March 4, 2019 23:42
@devversion devversion requested review from a team as code owners March 4, 2019 23:42
@devversion
Copy link
Member Author

devversion commented Mar 4, 2019

@IgorMinar @gkalpak I brought down the non-ivy docs example tests job to 3min and the Ivy docs examples to 4min.

This will be ultimately solved by Bazel anyway, but for now this is most likely even faster than with Bazel. so we have some good baseline and it helps with #28940 😁

Copy link
Member

@gkalpak gkalpak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left some minor comments. LGTM otherwise 👍

aio/tools/examples/run-example-e2e.js Outdated Show resolved Hide resolved
aio/tools/examples/run-example-e2e.js Show resolved Hide resolved
aio/tools/examples/run-example-e2e.js Outdated Show resolved Hide resolved
aio/tools/examples/run-example-e2e.js Outdated Show resolved Hide resolved
@devversion
Copy link
Member Author

@gkalpak Addressed your feedback. thanks!

Note: This PR still needs approval from fw-core and fw-i18n

Copy link
Contributor

@AndrewKushnir AndrewKushnir left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM from i18n side 👍

@gkalpak
Copy link
Member

gkalpak commented Mar 7, 2019

@AndrewKushnir, what about fw-core? 😁

@devversion
Copy link
Member Author

Yeah, still needs review from @angular/fw-core I think. Can someone please have a look?

Copy link
Contributor

@kara kara left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@kara kara added action: merge The PR is ready for merge by the caretaker target: major This PR is targeted for the next major release and removed action: review The PR is still awaiting reviews from at least one requested reviewer target: patch This PR is targeted for the next patch release labels Mar 12, 2019
@kara
Copy link
Contributor

kara commented Mar 12, 2019

caretaker note: merging to master branch since patch didn't apply cleanly. @devversion is creating a new PR for patch

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project cla: yes target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants