-
Notifications
You must be signed in to change notification settings - Fork 137
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
ci: use dockerLogs step #810
Conversation
💚 Build SucceededExpand to view the summary
Build stats
Test stats 🧪
Steps errorsExpand to view the steps failures
|
Codecov Report
@@ Coverage Diff @@
## master #810 +/- ##
=======================================
Coverage 92.66% 92.66%
=======================================
Files 50 50
Lines 2291 2291
Branches 456 456
=======================================
Hits 2123 2123
Misses 165 165
Partials 3 3 |
sleep randomNumber(min: 5, max: 10) | ||
if(env.MODE == 'saucelabs'){ | ||
withSaucelabsEnv(){ | ||
try { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is required to be able to run a post-build step within this method. We could potentially add this section to the post-build always step. What do you prefer?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alright, I'm afraid we cannot do the post-block though, the runAllScopes
runs several scopes in a loop :(
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe it's a good idea to have it in a post block, to always have it if needed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm worried about this one. Won't docker inspect
will dump all environment details? I'm concerned that we might end up leaking sensitive data. Even if that isn't the case now, we might accidentally forget that this is in place in the future.
What do you suggest? |
Sorry, I didn't see this comment earlier. I don't think we should ever do a |
should not be secrets references in the docker-compose.yml, and the ones that can contain are related to the local containers and do not give access anywhere. In some cases, we need the inspect to see the status of the container when it died, we can remove the environment from the inspect output when we generate the file. |
Parsing the output and removing the |
this makes the thing
|
* upstream/master: (23 commits) feat(rum-core): capture XHR/Fetch spans using resource timing (elastic#825) docs: update set-up.asciidoc (elastic#814) chore: remove compressed size gh workflow (elastic#828) feat: use page visibilityState for browser responsiveness check (elastic#813) ci(jenkins): report bundlesize as a GitHub comment (elastic#826) docs: release notes for 5.2.1 (elastic#824) chore(release): publish fix(rum-core): protect aganist buggy navigation timing data (elastic#819) fix(rum-core): protect aganist buggy navigation timing data (elastic#819) chore(rum-core): use startTime for LCP marks (elastic#815) fix(rum-core): capture tbt after all task entries are observed (elastic#803) feat(rum-react): use correct path when route is path array (elastic#800) ci: enable benchmark on a PR basis (elastic#812) ci: use dockerLogs step (elastic#810) fix: env var invalid type (elastic#809) fix: workarount for elastic/beats#18858 (elastic#807) docs: add release notes for 5.2.0 (elastic#801) chore(release): publish fix(rum-core): consider user defined type of high precedence (elastic#798) fix(rum): use single instance of apm across all packages (elastic#796) ...
What
It archives the docker container details for every stage that runs docker.
How to use it
artifact/docker-info
folderdocker-containers.txt
<id>.log
is the logs for the container withid
<id>-cmd.txt
is the docker container run parameters<id>-inspect.json
is the output of the docker inspect commandTests
(BO view)
Issues
Closes #806