shenwei356 / rush

A cross-platform command-line tool for executing jobs in parallel
https://github.com/shenwei356/rush
MIT License
846 stars 63 forks source link

How to understand which log belong to which input parameter? #38

Closed mrtdem closed 2 years ago

mrtdem commented 2 years ago

Hello there,

First of all thank you , rush is great problem solver tool. We trying to implement rush for multi cluster deployment on kubernetes and other internal deployments in parallel.

I use rush with this pattern echo -e "rollout status deployment/name-n xyznamespace\nrollout status deployment/name-n abcnamespace" | ./rush 'kubectl {}' This pattern work without any problem with rush. But with 2 or 3 input, logs are getting complicated and we can't follow which logs belong which input.

For example Can we add input parameter to beginning of the log like this [1. parameter] status is waiting [3. parameter] status is succeed [2. parameter] status is failed

What can be done to fix this problem. Can we achieve with current version of rust? If development is needed, i would be very happy to contribute

bburgin commented 2 years ago

Can you try the --immediate-output argument?

mrtdem commented 2 years ago

Thank you @bburgin . --immediate-output parameter solved my problem. It's add [cmdID,tryNumber,lineNumber] before the output.

shenwei356 commented 2 years ago

Thank you @bburgin !