question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Regression - Cypress executor does not respect env cli parameters.

See original GitHub issue

Current Behavior

Regression of https://github.com/nrwl/nx/issues/9764. I upgraded from 14.2.4 where it worked.

Expected Behavior

Steps to Reproduce

This issue may not be prioritized if details are not provided to help us reproduce the issue.

Failure Logs

Environment

   Node : 16.13.0
   OS   : darwin x64
   yarn : 3.2.1
   
   nx : 14.3.6
   @nrwl/angular : Not Found
   @nrwl/cypress : 14.3.6
   @nrwl/detox : Not Found
   @nrwl/devkit : 14.3.6
   @nrwl/eslint-plugin-nx : 14.3.6
   @nrwl/express : Not Found
   @nrwl/jest : 14.3.6
   @nrwl/js : 14.3.6
   @nrwl/linter : 14.3.6
   @nrwl/nest : Not Found
   @nrwl/next : Not Found
   @nrwl/node : 14.3.6
   @nrwl/nx-cloud : Not Found
   @nrwl/nx-plugin : Not Found
   @nrwl/react : 14.3.6
   @nrwl/react-native : Not Found
   @nrwl/schematics : Not Found
   @nrwl/storybook : 14.3.6
   @nrwl/web : 14.3.6
   @nrwl/workspace : 14.3.6
   typescript : 4.7.4
   ---------------------------------------
   Community plugins:
         nx-stylelint: 13.4.0

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:29 (23 by maintainers)

github_iconTop GitHub Comments

2reactions
barbados-clemenscommented, Aug 15, 2022

@danr-za that’s very interesting. presumably that should have just worked anyways, and also the fact it’s influencing the --env params is also interesting. I’ll investigate some on my side to see what I find, thanks for more info.

I assume that they are only logged this way --env=[object Object] but actually are passed correctly.

Correct, they will be still be passed to the executors as expected, unless you use DTE, where they are currently getting mangled, but presumably this recent change made will fix that.

I also have a PR up to document usage patterns with env that adds using --env.<value> to the cypress e2e tests so we can prevent any other regressions.

1reaction
danr-zacommented, Aug 13, 2022

Hmm not us

Read more comments on GitHub >

github_iconTop Results From Across the Web

Environment Variables | Cypress Documentation
In Cypress, "environment variables" are variables that are accessible via Cypress.env . These are not the same as OS-level environment variables.
Read more >
End-to-end testing with GitLab CI/CD and WebdriverIO
Confidence checking your entire app every time a new feature is added can quickly become repetitive. Learn how to automate it with GitLab...
Read more >
Ceph Dashboard Developer Documentation
Feature Design . To promote collaboration on new Ceph Dashboard features, the first step is the definition of a design document. These...
Read more >
Test splitting and parallelism - CircleCI
A guide for test splitting and running tests across parallel compute environments to optimize your CircleCI pipelines.
Read more >
How To Setup JUnit Environment For Your First Test?
Instead, a single Hamcrest jar file has to be downloaded so that you can execute the JUnit tests in Eclipse, IntelliJ, and on...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found