Followup work on setup github actions#7431
Conversation
8cb5fd6 to
1ce0209
Compare
1ce0209 to
412bb10
Compare
This comment has been minimized.
This comment has been minimized.
|
Let's start removing the common ones.. |
|
@lipis You mean azure pipelines? |
|
Yes |
|
How about remove it in a separate PR? |
89c0325 to
0e65dbf
Compare
0e65dbf to
254278e
Compare
|
Yes maybe.. let's finalize the gh ones.. |
|
@lipis Please add a |
33e680e to
b410b12
Compare
7d88632 to
a3d7b80
Compare
46c4b61 to
877814c
Compare
877814c to
e13fc68
Compare
|
All green! That means we are ready to get rid of Azure? or they are still doing something more than we do with GitHub? |
|
@lipis All azure jobs covered, problem is github actions seems slower than azure, especially the one collects coverage. |
|
I would still go with GitHub... |
|
I use github actions too. Seems faster with |
|
Let me know when we can disable Azure :) |
|
Just remove the .azure directory and we should be fine when you're ready. |
|
Let's disable it in #7824 , shall we? |
| "jest-watch-typeahead/testname", | ||
| ], | ||
| reporters: ["default"].concat(ENABLE_TEST_RESULTS ? "jest-junit" : []), | ||
| verbose: true, |
There was a problem hiding this comment.
Could we remove this verbose: true? Now Jest prints too much when I run it locally.
There was a problem hiding this comment.
How about set to isCI, yarn test will print less, and yarn test --verbose can still print more
Todo:
ci-infoinstead ofis-ci#7432 & Always enableENABLE_TEST_RESULTSandAST_COMPAREon CI #7433#7321