Paul Gschwendtner ab930cf87b build: publish artifacts based on branch (#9919) ...

Build artifacts will be published differently for different branches. For example, commits in `master` will be published on the `master` branch on the `*-builds` repository. `5.2.x` commits will be published on the `5.2.x` branch on the `*-builds` repository.

Tags on the build repositories will be explicit to indicate from what branch they come. The version placeholders (in the build output) will be similar as before, and won't contain any information about the branch. e.g. `5.2.x-5.2.1-43s435s` will look bad.

2018-02-13 10:35:40 -08:00

..

browserstack

build: shorter wait delay for tunnels (#6607)

2017-08-23 11:30:49 -07:00

caretaking

chore: add script to generate presubmit scheduler script (#8581)

2017-12-20 10:33:49 -08:00

ci

build: don't skip master build when only md files have changed (#9879)

2018-02-13 07:52:19 -08:00

closure-compiler

feat: angular 5 support (#6018)

2017-11-01 11:03:57 -07:00

deploy

build: publish artifacts based on branch (#9919)

2018-02-13 10:35:40 -08:00

saucelabs

build: update sauce connect (#8438)

2017-11-14 11:22:41 -08:00

retry-call.sh

build(): retries for travis deploying (#7146)

2017-09-29 13:23:52 -07:00