add step to compress before publishing artifacts to appveyor #1029
Conversation
syamgk
added
the
do-not-merge/work-in-progress
|
Code Climate has analyzed commit f47a5a9 and detected 0 issues on this pull request. View more on Code Climate. |
|
✅ odo build 500 completed and artifacts can be found here (for commit 59bc265164 by @syamgk) |
syamgk
removed
the
do-not-merge/work-in-progress
syamgk
changed the title
appveyor.yml
Outdated
| @@ -32,12 +32,19 @@ test_script: | |||
| build_script: | |||
| - make cross | |||
|
|
|||
| after_build: | |||
There was a problem hiding this comment.
Wouldn't it be better to run this after tests (after_test)?
Currently, it builds binaries, than gzips it, and then run tests. But gzipping doesn't make sense if tests don't pass.
Codecov Report
@@ Coverage Diff @@
## master #1029 +/- ##
==========================================
- Coverage 46.24% 46.12% -0.12%
==========================================
Files 21 21
Lines 3419 3419
==========================================
- Hits 1581 1577 -4
- Misses 1678 1682 +4
Partials 160 160
Continue to review full report at Codecov.
|
syamgk
force-pushed
the
gzip-artifacts-appve
branch
from
75a2336
to
395240d
Compare
add step to compress before publishing artifacts to appveyor
syamgk
force-pushed
the
gzip-artifacts-appve
branch
from
395240d
to
f47a5a9
Compare
|
✅ odo build 502 completed and artifacts can be found here (for commit d339dcc294 by @syamgk) |
add step to compress before publishing artifacts to appveyor
What is the purpose of this change? What does it change?
to reduce the storage consumption on appveyor
Was the change discussed in an issue?
#1025
How to test changes?
check if artifacts are publishing on appveyor in a compressed form and validate the binaries