Bundle update output order

[collimarco]

Some weeks ago the output of bundle update has changed.

Instead of having Fetching gem X and then immediately Installing gem X, we now have the output in a confused order...

Example (difficult to understand):

Fetching gem X
Fetching gem Y
Installing gem X
Fetching gem Z
Installing gem Y
Installing gem Z

Is there any way to get the output in the correct order, which is extremely more readable?

Example (much more readable):

Fetching gem X
Installing gem X
Fetching gem Y
Installing gem Y
Fetching gem Z
Installing gem Z

[simi]

If I remember well, this is caused by parallel installation. If you prefer slower, but properly "ordered" output, you can limit to only 1 job.

       --jobs=[<number>], -j[<number>]
              The maximum number of parallel download and install jobs. The default is 1.

[collimarco]

So if I don't pass -j the default should be 1... however the order of the output is in random order. What should I do?

[deivid-rodriguez]

No, the default value is only 1 on Windows, because of some issues we found with parallel installation. On other platforms, bundle install runs at "full speed" by default. We have an issue to improve this: #3305.

[deivid-rodriguez]

I just checked the Windows situation. We did keep the 1 default for a while to prevent those issues I mentioned, but we have been running CI with parallel installation by default for months and it seems all good, so the default will be flipped to the number of processors on Windows too in bundler 2.3.0.

[collimarco]

Is there any way/option to have only 1 line of output for each gem? Or at least to have fetching and installing in two consecutive lines?

[deivid-rodriguez]

Your suggestion is duly noted. In the meantime, feel free to configure jobs to be 1 so you can get an ordered output.

[deivid-rodriguez]

Closing in favor of #3305.