Add --no-progress to gatsby build for less verbose build output

[brettinternet]

Summary

Currently, the gatsby build command is particularly verbose with progress updates. This causes heavy output for dumb terminals like Jenkins which print a new line for every animation:

Current workaround

I was fortunate to find an open issue analyzing the effects of Ink on the the build time. I found the suggestion to set an environment variable CI=true.

So to my build script looks like this:

cross-env CI=true gatsby build

Basic example

It seems a --no-progress or --quiet option similar to the npm arg should be available to gatsby build.

Would having a --no-progress build argument setting the CI environment variable be appropriate?

Motivation

An alternative solution would be to hold the CI environment variable as a feature and document it. While it's a workaround for me, I worry about the functionality changing since it's not a documented feature. @wardpeet pointed out that most CI vendors enable CI=true, but I wasn't aware of this. We use a self-hosted instance of Jenkins rather than a CI vendor.

---

Thank you to the contributors for all your attention to such an awesome project!

[bitttttten]

Looks like an issue with https://github.com/sindresorhus/ora no? IIRC that is the library used for the progress spinner.

[sidharthachatterjee]

An alternative solution would be to hold the CI environment variable as a feature and document it. While it's a workaround for me, I worry about the functionality changing since it's not a documented feature. @wardpeet pointed out that most CI vendors enable CI=true, but I wasn't aware of this. We use a self-hosted instance of Jenkins rather than a CI vendor.

Not sure about --no-progress but this is a good idea. Would you like to open an PR documenting it?

[gagandeepp]

can i taket a look on this one?

[sidharthachatterjee]

Documented in #17966

Let's close this for now