Skip to content

build: Disable cargo progress in CI jobs using tty#1419

Closed
ronh-rs wants to merge 1 commit intoI67a788f80925bd2d075d9a0443b44835d90b168dfrom
I9453179b4294fefd003bf370c5184adf20a4a7a6
Closed

build: Disable cargo progress in CI jobs using tty#1419
ronh-rs wants to merge 1 commit intoI67a788f80925bd2d075d9a0443b44835d90b168dfrom
I9453179b4294fefd003bf370c5184adf20a4a7a6

Conversation

@ronh-rs
Copy link
Collaborator

@ronh-rs ronh-rs commented Jan 14, 2025

Some buildkite jobs using the docker-compose plugin have tty on because
it results in colored output. However, if cargo detects tty, it creates
progress bars... which are wholly unnecessary in CI jobs. This update
sets CARGO_TERM_PROGRESS_WHEN=never when enabling tty in the
docker-compose plugin.

Some buildkite jobs using the docker-compose plugin have tty on because
it results in colored output.  However, if cargo detects tty, it creates
progress bars... which are wholly unnecessary in CI jobs.  This update
sets CARGO_TERM_PROGRESS_WHEN=never when enabling tty in the
docker-compose plugin.

Change-Id: I9453179b4294fefd003bf370c5184adf20a4a7a6
Reviewed-on: https://gerrit.readyset.name/c/readyset/+/8625
Tested-by: Buildkite CI
Reviewed-by: Michael Zink <michael.z@readyset.io>
@ronh-rs ronh-rs closed this May 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments