Paul Gschwendtner 8badf9808a build: add pre-release check that validates the version name (#29551) ... Currently with the release of "8.0.0-beta.10", the Bazel npm packag accidentally was stamped with an incorrect version placeholder: `8.0.0-beta.10+1.sha-a28b3e3`. This can happen because the placeholder is based on latest tag that matches the Semver format. e.g. if `HEAD` equals to the commit that has the latest tag, the version name will be correct and refer to the tag name (e.g. `8.0.0-beta.10`). Though if the latest commit is not tagged with the most recent tag, the version name will also include the SHA of the commit (e.g. `8.0.0-beta.10+1.sha-a28b3e3`). We can ensure that we don't accidentally release versions from a more recent commit that shouldn't be part of the release by adding a pre-release check that ensures that the `BUILD_SCM_VERSION` Bazel status variable matches the expected version format. PR Close #29551		2019-03-27 12:26:13 -07:00
..
browserstack	ci: clean up CI logging, folding, add build time logging, and improve error handling (#14425)	2017-03-02 00:22:24 -08:00
ci	ci: do not cache modified "node_modules" in "material-unit-tests" job (#29416)	2019-03-20 06:58:23 -07:00
git	fix: missing semi-colon and empty line (#26945)	2018-11-05 11:37:55 -08:00
github	ci: add a rebase check to the merge-pr script (#28250)	2019-01-22 09:26:53 -08:00
jenkins	fix(build): make perf tests work again	2015-02-27 15:22:19 -08:00
release	build: add pre-release check that validates the version name (#29551)	2019-03-27 12:26:13 -07:00
saucelabs	ci: disable sauce-connect ssl bumping (#29447)	2019-03-21 22:18:18 +00:00
windows	ci: add codefresh (#29305)	2019-03-21 22:19:19 +00:00
build-ivy-npm-packages.sh	build: allow build-packages-dist.sh to be run from anywhere (#29092)	2019-03-20 14:45:54 -04:00
build-packages-dist.sh	build: allow build-packages-dist.sh to be run from anywhere (#29092)	2019-03-20 14:45:54 -04:00
package-builder.sh	build: run angular/material2 unit tests on ci (#28197)	2019-02-01 12:15:35 -05:00