Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upOutput logs from s3-npm-publish Docker container #318
Conversation
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
codecov-io
Mar 28, 2017
Codecov Report
Merging #318 into master will not change coverage.
The diff coverage isn/a.
@@ Coverage Diff @@
## master #318 +/- ##
======================================
Coverage 76.6% 76.6%
======================================
Files 120 120
Lines 5887 5887
Branches 959 959
======================================
Hits 4510 4510
Misses 1377 1377Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact),ø = not affected,? = missing data
Powered by Codecov. Last update 54519c6...2a7a425. Read the comment docs.
codecov-io
commented
Mar 28, 2017
Codecov Report
@@ Coverage Diff @@
## master #318 +/- ##
======================================
Coverage 76.6% 76.6%
======================================
Files 120 120
Lines 5887 5887
Branches 959 959
======================================
Hits 4510 4510
Misses 1377 1377Continue to review full report at Codecov.
|
chdorner
approved these changes
Mar 29, 2017
If the Jenkins build output is what you expect, then please go ahead an merge.
robertknight commentedMar 28, 2017
•
edited
To help debug publishing failures, output logs from the container. See
https://hypothes-is.slack.com/archives/C076LQFA4/p1490705667081734
See https://go.cloudbees.com/docs/cloudbees-documentation/cje-user-guide/index.html#docker-workflow-sect-run for docs on the Jenkins plugin that we use to run Docker. Note that unlike the example they give, I use
--followto make sure that we output all of the logs until the task exits.