docs: update the continuous integration story

[CharlesSuttie]

This PR aims to update the CircleCi and Travis configurations in the continuous integration story.

The main changes are:

• update ng test and ng e2e command flags for version 6
• use npm ci instead of npm install
• use headless chrome instead of chrome

To assist review:

• a link to the story in my fork is here.
• A demo Angular Cli app has been created using the new instructions and configuration files proposed by this PR.

I have endeavored to maintain the style and simplicity of the story. All comments are very welcome.

@filipesilva, I noticed this comment and would be happy to include what you said in this PR.

I feel this PR closes #10677 because the essential problem there was that the flags for the ng test and ng e2e commands changed with version 6. This PR also builds on #11445 and updates the ng test --browsers flag and the ng e2e --protractor-config flag, bringing the flags up to date with version 6.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

[CharlesSuttie]

I signed it!

[googlebot]

CLAs look good, thanks!

[filipesilva]

Heya, thanks for updating this!

I left a question about npm ci, a naming nitpick, and since you mentioned #11116 (comment) I would like to ask you to add it to.

Using ChromeHeadless has some caveats to it (see https://github.com/angular/protractor/blob/master/docs/browser-setup.md#using-headless-chrome) but I think for most users it should be ok so no need to highlight it.

I also feel you've succeeded in maintaining the style of the original doc, cheers!

[filipesilva]

Have you checked if npm ci is faster than using cache on the CI? Last time I checked npm ci was much slower.

[CharlesSuttie]

Yes, you're quite right, using the cache is much faster.

[filipesilva]

Nit: what do you think of ChromeHeadlessCI instead? I feel the my prefix doesn't say much about what's going on.

[markgoho]

When you provide only the major version, docker will always choose the most recent version.
E.g. image: circleci/node:10-browsers and then running node -v yields: v10.6.0

I would recommend reverting this change back to - image: circleci/node:8-browsers

[CharlesSuttie]

Thanks @markgoho, good point!

[filipesilva]

I think the changes look good, but due to the way we parse commit messages you will need to squash all of these into a single commit.

I think the easiest way to do this is rebasing and marking the second and third commits as fixups.

[CharlesSuttie]

Thanks @filipesilva ! I've rebased, squashed the commits into a single commit with an updated message (to remove the reference to npm ci and add a reference to the guidance on ChromeDriver). This is my first time contributing and I'm not totally confident I have the git part the way you would like, so please forgive me if I've made a mistake here.

[filipesilva]

The rebase went well, cheers!

[angular-automatic-lock-bot]

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.}