Skip to content

Jenkins recognized as Hudson #170

@Michsior14

Description

@Michsior14

Environment

Latest, Node 22.21.0

Reproduction

Simply check provider during jenkins pipeline execution.

import { provider } from 'std-env';
console.log(provider);

Describe the bug

Currently the providers are recognized based on alphabetical order of config declaration. This causes Jenkins to be recognized as Hudson as Jenkins still provides fallback environment variables for compatibility reasons.

Additional context

No response

Logs

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions