-
-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Speedup pipelines #1168
Speedup pipelines #1168
Conversation
7cc0af1
to
6d968fe
Compare
6d968fe
to
f134e22
Compare
35b3c8c
to
2a46908
Compare
1c0010f
to
0b57e90
Compare
62b7977
to
4f98185
Compare
4f98185
to
d80f38a
Compare
@Mimetis This should fix the pipelines and also improve them a bunch. And it closes two of the issues I just opened. Those have some explanation of the justifications. The cache step may need some tweaking because I'm not sure if it is working. |
9682ee9
to
ff39ae8
Compare
a68e891
to
8926277
Compare
8926277
to
48db446
Compare
@Mimetis this should make the pipelines green. I just resolved the conflicts from today. |
@symbiogenesis nice, I'll look this week end for sure |
b4cb0fe
to
bd5e838
Compare
Hey @symbiogenesis , I'm struggling a little bit with the tests pipelines since this PR Seems the tests are not run when targeting .net core 3.1
Any idea ? |
hum I don't know what I've done, but it's working now :) |
This may go some ways towards speeding up the pipelines
I think it will save a couple minutes per pipeline. Refactoring the tests, as described in #1162 would help more substantially.
The cache step won't save any time on the first run, but subsequent runs will benefit.
Generating lockfiles was necessary in order to create a perfect cache key
Fixes #1167 and #1165