cargdev/angular
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

ci: publish build snapshots from Bazel/CircleCI (#23512)

Browse Source 
This uses a new script and CircleCI job called "build-packages-dist"
which shims the new Bazel build to produce outputs matching the legacy
build. We'll use this to get AIO testing onto CircleCI as well.

We move the integration tests to a new circleCI job that depends on this
one, as well as the build publishing job.

Note that every PR will have a trivial green publishing status, because
we always create this job even for PRs. We'd rather not - see
https://discuss.circleci.com/t/workflows-pull-request-filter/14396/4

PR Close #23512
This commit is contained in:
Alex Eagle
2018-04-23 11:46:02 -07:00
committed by Victor Berchet
parent 60e5507076
commit b26ac1c22f
8 changed files with 143 additions and 84 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
docs/DEVELOPER.md
View File

@ -133,11 +133,10 @@ $ gulp lint
## Publishing snapshot builds
When the `master` branch successfully builds on Travis, it automatically publishes build artifacts
When a build of any branch on the upstream fork angular/angular is green on CircleCI,
it automatically publishes build artifacts
to repositories in the Angular org, eg. the `@angular/core` package is published to
http://github.com/angular/core-builds.
The ES2015 version of Angular is published to a different branch in these repos, for example
http://github.com/angular/core-builds#master-es2015
You may find that your un-merged change needs some validation from external participants.
Rather than requiring them to pull your Pull Request and build Angular locally, you can