Skip to content

Sentry fails to install/run around 30% of the time when using sentrycli_cdnurl #1758

@RossMcMillan92

Description

@RossMcMillan92

Environment

Jenkins
Using @sentry/next
Using artifactory (changing the URL with sentrycli_cdnurl)

Steps to Reproduce

Around 30% of our builds fail with:

Error: Unexpected sentry-cli version "", expected "1.75.2"

I suspect it's because we're altering the download location with sentrycli_cdnurl, however, I don't think artifactory is the issue as all our other dependencies (including a few others with binaries) install without issue. Seems like a race condition somewhere.

Expected/Actual Result

The package would install and run correctly.

Logs

15:57:55  error /home/jenkins/agent/workspace/XXX-ci-cd/YYY-pipeline/node_modules/@sentry/webpack-plugin/node_modules/@sentry/cli, /home/jenkins/agent/workspace/XXX-ci-cd/YYY-pipeline/node_modules/@sentry/wizard/node_modules/@sentry/cli: Command failed.
15:57:55  Exit code: 1
15:57:55  Command: node ./scripts/install.js
15:57:55  Arguments: 
15:57:55  Directory: /home/jenkins/agent/workspace/XXX-ci-cd/YYY-pipeline/node_modules/@sentry/wizard/node_modules/@sentry/cli
15:57:55  Output:
15:57:55  [sentry-cli] Using cached binary: /home/jenkins/.npm/sentry-cli/65305f-sentry-cli-Linux-x86-64
15:57:55  Error: Unexpected sentry-cli version "", expected "1.75.2"

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions