Giter VIP home page Giter VIP logo

Comments (7)

KevinGrandon avatar KevinGrandon commented on August 26, 2024 1

Thanks for checking in. The captures artifacts are better than noting, but a way to configure live output of service logs would be really welcome. If there was something that wasn’t a crazy amount of effort but provided live service output that would be really useful.

Maybe just an option to background tail all logs before execution?

from docker-compose-buildkite-plugin.

KevinGrandon avatar KevinGrandon commented on August 26, 2024

Perhaps there would be some way to do this in userland if we had #47, though multiple logs per job would be even more amazing.

from docker-compose-buildkite-plugin.

lox avatar lox commented on August 26, 2024

Sorry for the delay responding @KevinGrandon. I like the suggestion of the top-level logs block!

from docker-compose-buildkite-plugin.

lox avatar lox commented on August 26, 2024

Currently we capture logs of dependant services as artifacts on failure, is this not adequate @KevinGrandon? The more I look at this, the gnarlier it is to implement.

from docker-compose-buildkite-plugin.

lox avatar lox commented on August 26, 2024

Maybe just an option to background tail all logs before execution?

I'll look into this, but the issues is that docker-compose run creates ephemeral services that can't easily be docker-compose log -f'd. I'll look for a workaround.

from docker-compose-buildkite-plugin.

lox avatar lox commented on August 26, 2024

Also docker-compose logs and docker logs will exit if the containers or services aren't running yet.

from docker-compose-buildkite-plugin.

toote avatar toote commented on August 26, 2024

While I do believe that there are situations when something like this can be helpful, as mentioned back in 2018, logs as artifacts uploaded after the fact appear to have been enough.

I've been investigating a way to implement this but I can't think of a way to do this while still allowing the plugin to continue to run according to the main application container and shut down services afterwards with the current plugin structure. Add to that the fact that output for the main application as well as all other containers will probably be interleaved and would make it a nightmare to differentiate between them live.

Closing for now

from docker-compose-buildkite-plugin.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.