angular-cn/aio
Georgios Kalpakas d263595c63 ci(aio): do not fail when re-deploying preview for the same PR/SHA
Previously, when trying to upload the build artifacts for a PR/SHA that was
already successfully deployed (e.g. when re-running a Travis job), the preview
server would return a 403 and the build would fail.

Since we have other mechanisms to verify that the PR author is trusted and the
artifacts do indeed come from the specified PR and since the new artifacts
should be the same with the already deployed ones (same SHA), there is no reason
to fail the build. The preview server will reject the request with a special
HTTP status code (409 - Conflict), which the `deploy-preview` script will
recognize and exit with 0.
2017-04-13 11:26:21 +01:00
..
aio-builds-setup ci(aio): do not fail when re-deploying preview for the same PR/SHA 2017-04-13 11:26:21 +01:00
content hr update 2017-04-12 21:10:05 +01:00
e2e feat(aio): marketing page styles 2017-04-03 15:48:52 -07:00
scripts ci(aio): do not fail when re-deploying preview for the same PR/SHA 2017-04-13 11:26:21 +01:00
src test(aio): add sidenav tests and refactor related tests 2017-04-12 14:17:14 -07:00
tools docs(aio): final migration from old site 2017-04-12 21:01:55 +01:00
transforms build(aio): remove unused Rho package 2017-04-12 12:24:02 -07:00
.angular-cli.json feat(aio): improve ProgressiveWepApp-ability (#15628) 2017-03-30 12:35:15 -07:00
.firebaserc build(aio): big move of docs related files (#14361) 2017-02-09 11:58:36 -08:00
.gitignore build(aio): update project config for @angular/cli v1.0.0 2017-03-27 11:55:26 -07:00
README.md build(aio): big move of docs related files (#14361) 2017-02-09 11:58:36 -08:00
database.rules.json build(aio): big move of docs related files (#14361) 2017-02-09 11:58:36 -08:00
firebase.json fix(aio): do not fallback to `index.html` for file requests (#15401) 2017-03-22 15:31:47 -07:00
karma.conf.js build(aio): update project config for @angular/cli v1.0.0 2017-03-27 11:55:26 -07:00
ngsw-manifest.json feat(aio): support @angular/service-worker using the CLI generated service worker manifest (#15042) 2017-03-10 14:05:29 -08:00
package.json build(aio): upgrade to @angular/material#2.0.0-beta.3 (#15606) 2017-04-12 12:25:11 -07:00
protractor.conf.js build(aio): update project config for @angular/cli v1.0.0 2017-03-27 11:55:26 -07:00
tsconfig.json build(aio): update project config for @angular/cli v1.0.0 2017-03-27 11:55:26 -07:00
tslint.json test(aio): enable tslint rule for focused jasmine tests/suites 2017-04-01 20:56:16 +01:00
yarn.lock build(aio): upgrade to @angular/material#2.0.0-beta.3 (#15606) 2017-04-12 12:25:11 -07:00

README.md

Site

This project was generated with angular-cli version 1.0.0-beta.26.

Development server

Run ng serve for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.

Code scaffolding

Run ng generate component component-name to generate a new component. You can also use ng generate directive/pipe/service/class/module.

Build

Run ng build to build the project. The build artifacts will be stored in the dist/ directory. Use the --prod flag for a production build.

Running unit tests

Run ng test to execute the unit tests via Karma.

Running end-to-end tests

Run ng e2e to execute the end-to-end tests via Protractor. Before running the tests make sure you are serving the app via ng serve.

Deploying to GitHub Pages

Run ng github-pages:deploy to deploy to GitHub Pages.

Further help

To get more help on the angular-cli use ng help or go check out the Angular-CLI README.