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

Fix angular-bazel-example CI #792

Merged
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 34 additions & 1 deletion .circleci/config.yml
Original file line number Diff line number Diff line change
Expand Up @@ -299,10 +299,36 @@ jobs:
- *attach_workspace
- *init_environment
- *init_bazel
- run: ./scripts/setup_examples_angular.sh
# Some examples such as app require xvfb
- run: xvfb-run -a ./scripts/test_examples_all.sh ${CIRCLE_NODE_INDEX} ${CIRCLE_NODE_TOTAL}

# This job cannot run on BuildKite (BazelCI) because it requires changing
# directories to test inside nested workspaces.
# See https://github.com/bazelbuild/continuous-integration/issues/225
test_angular_bazel_example:
<<: *job_defaults
docker:
# Needed because some tests require local chrome
- image: *browsers_docker_image
resource_class: xlarge
steps:
- *attach_workspace
- *init_environment
- *init_bazel
- run: ./scripts/setup_examples_angular.sh
- run:
name: Test angular-bazel-example
command: |
cd ./examples/angular
../../scripts/link_deps.sh
# Install Bazel from NPM
yarn
# Build and Test
yarn ng test
yarn ng e2e
# Also run prodserver test which is not covered by `ng e2e`
yarn bazel test //e2e:prodserver_test

workflows:
version: 2
default_workflow:
Expand Down Expand Up @@ -356,3 +382,10 @@ workflows:
- build_jasmine_package
- build_labs_package
- build_karma_package
- test_angular_bazel_example:
requires:
- build_release
- build_typescript_package
- build_jasmine_package
- build_labs_package
- build_karma_package