Cypress: Collect CI environment variable from Concourse CI

Created on 4 Jun 2019  路  4Comments  路  Source: cypress-io/cypress

Current behavior:

We don't collect anything from a Concourse CI run - do not even know if they are running within Concourse CI

Desired behavior:

Need to identify Concourse and pull any useful environment variables for use here:

https://github.com/cypress-io/cypress/blob/issue-3909/packages/server/lib/util/ci_provider.js

Add environment variables to collect from https://concourse-ci.org/implementing-resource-types.html#resource-metadata

  • $BUILD_ID
  • $BUILD_NAME
  • $BUILD_JOB_NAME
  • $BUILD_PIPELINE_NAME
  • $BUILD_TEAM_NAME
  • $ATC_EXTERNAL_URL

If the build is a one-off, $BUILD_NAME, $BUILD_JOB_NAME, and $BUILD_PIPELINE_NAME will not be set.

I see quite a few other env variables floating around starting with CONCOURSE_, which can probably be used to identify it as a run within Concource CI.

Versions

Cypress 3.3.1

concourse first-timers-only pkserver enhancement

Most helpful comment

@mster Thanks! We would love an open PR - even one that is a work in progress is fine. Check out our contributing doc and ask us if you get stuck.

All 4 comments

I'd love to help contribute! :)

@mster Thanks! We would love an open PR - even one that is a work in progress is fine. Check out our contributing doc and ask us if you get stuck.

The code for this is done in cypress-io/cypress#4642, but has yet to be released.
We'll update this issue and reference the changelog when it's released.

Released in 3.4.0.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

zbigniewkalinowski picture zbigniewkalinowski  路  3Comments

jennifer-shehane picture jennifer-shehane  路  3Comments

igorpavlov picture igorpavlov  路  3Comments

brian-mann picture brian-mann  路  3Comments

stormherz picture stormherz  路  3Comments