build: use bazel version from node modules (#26691)
* No longer depends on a custom CircleCI docker image that comes with Bazel pre-installed. Since Bazel is now available through NPM, we should be able to use the version from `@bazel/bazel` in order to enforce a consistent environment on CI and locally. * This also reduces the amount of packages that need to be published (ngcontainer is removed) PR Close #26691
This commit is contained in:

committed by
Matias Niemelä

parent
cd444bc2ba
commit
c44b93253c
@ -7,7 +7,6 @@
|
||||
*/
|
||||
|
||||
import * as fs from 'fs';
|
||||
import * as path from 'path';
|
||||
import {SymbolExtractor} from './symbol_extractor';
|
||||
|
||||
if (require.main === module) {
|
||||
@ -44,7 +43,7 @@ function main(argv: [string, string, string] | [string, string]): boolean {
|
||||
const defineFlag = (compile !== 'legacy') ? `--define=compile=${compile} ` : '';
|
||||
console.error(`TEST FAILED!`);
|
||||
console.error(` To update the golden file run: `);
|
||||
console.error(` bazel run ${defineFlag}${process.env['BAZEL_TARGET']}.accept`);
|
||||
console.error(` yarn bazel run ${defineFlag}${process.env['BAZEL_TARGET']}.accept`);
|
||||
}
|
||||
}
|
||||
return passed;
|
||||
|
Reference in New Issue
Block a user