Skip to content

Enable CARGO_TERM_COLOR automatically in GitLab CI #16969

New issue
New issue
Open
Open
Enable CARGO_TERM_COLOR automatically in GitLab CI#16969
Labels
A-console-outputArea: Terminal output, colors, progress bar, etc.C-feature-requestCategory: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`S-triageStatus: This issue is waiting on initial triage.

Description

@TheJanzap
TheJanzap
opened on May 6, 2026

Problem

I would like to have automatic colored output from Cargo in GitLab CI. Currently, I have to manually set CARGO_TERM_COLOR: always in my CI config to enable it. This would be a nice convenience feature to have.

Proposed Solution

Detect if Cargo is running in GitLab CI/CD and enable colored output.

Notes

No response

Activity

  1. TheJanzap
    added
    C-feature-requestCategory: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`
    S-triageStatus: This issue is waiting on initial triage.
    on May 6, 2026

  2. weihanglo commented on May 6, 2026

    @weihanglo
    weihanglo
    on May 6, 2026
    Member

    While color in the GitLab UI can be nicer (as well as in GitHub Actions UI), enabling it by default also changes the raw log output as ANSI escape sequences will always appear in it. It is not everyone wants and could be considered as a breaking change.

    Since Cargo already supports explicit opt-in via term.color config and equivalent environment variable, the feature request feels hard to me to justify. Also, if we really want this, we should have a broader CI-color policy rather than a vendor-specific behavior.

  3. weihanglo
    added
    A-console-outputArea: Terminal output, colors, progress bar, etc.
    on May 6, 2026

  4. rami3l commented on Aug 25, 2026

    @rami3l
    rami3l
    on Aug 25, 2026
    Member

    @weihanglo Given the current consensus that rustup should provide relevant basic CI setup for the whole Rust installation, maybe we can close this in favor of rust-lang/rustup#5011?

  5. weihanglo commented on Aug 25, 2026

    @weihanglo
    weihanglo
    on Aug 25, 2026
    Member

    Sounds right. Closing

  6. weihanglo
    closed this as a duplicateof Provide a built-in way for rustup to adapt to a CI environment rustup#5011 on Aug 25, 2026

  7. epage commented on Aug 25, 2026

    @epage
    epage
    on Aug 25, 2026
    Contributor

    There is consenus on this? We've already started adding CI detection to cargo.

  8. weihanglo commented on Aug 25, 2026

    @weihanglo
    weihanglo
    on Aug 25, 2026
    Member

    No problem to keep this open for more discussions. Reopening.

  9. weihanglo
    reopened this on Aug 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-console-outputArea: Terminal output, colors, progress bar, etc.C-feature-requestCategory: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`S-triageStatus: This issue is waiting on initial triage.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions