honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/.codefresh
History
Alan Agius 660a091f41 ci: increase codefresh memory limit to decrease flakyness of known big tests (#30472) 
Such tests are:
```
//packages/language-service/test:test
//packages/bazel/test/ngc-wrapped:ngc_test
```

PR Close #30472
 		2019-05-17 13:34:11 -07:00
..
Dockerfile.win-1809 ci: update windows docker image for codefresh (#30472) 2019-05-17 13:34:11 -07:00
README.md ci: add codefresh badge (#29475) 2019-03-25 09:23:48 -07:00
bazel.rc ci: increase codefresh memory limit to decrease flakyness of known big tests (#30472) 2019-05-17 13:34:11 -07:00
codefresh.yml ci: include more tests in windows ci (#30472) 2019-05-17 13:34:11 -07:00
fix-msys64.cmd ci: add codefresh (#29305) 2019-03-21 22:19:19 +00:00

README.md

CodeFresh configuration

Codefresh build status

This folder contains configuration for the CodeFresh based CI checks for this repository.

The build pipeline

CodeFresh uses a several pipeline for each repository. The codefresh.yml file defines pipeline build steps for this repository.

Run results can be seen in the GitHub checks interface and in the public pipeline

Although most configuration is done via pipeline.yml, some options are only available in the online pipeline settings, which needs a login to access.

Caretaker

CodeFresh status can be found at http://status.codefresh.io/.

Issues related to the CodeFresh setup should be escalated to the Tools Team via the current caretaker, followed by Alex Eagle and Filipe Silva.

Rollout strategy

Currently it is only used for tests on Windows platforms, on the master branch, and without pushing user-facing reports. It's only possible to see current builds in the public pipeline dashboard.

After a week or two of running like this, we should reassess how stable and reliable it is.

Next steps include:

  • building PRs
  • showing build status publicly
  • blocking PRs that break the build
  • expanding the test suite