Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nx: task-runner#run-command always ignores outputStyle on CI #15570

Open
Hotell opened this issue Mar 9, 2023 · 6 comments
Open

nx: task-runner#run-command always ignores outputStyle on CI #15570

Hotell opened this issue Mar 9, 2023 · 6 comments
Assignees
Labels
scope: core core nx functionality type: feature

Comments

@Hotell
Copy link
Contributor

Hotell commented Mar 9, 2023

Current Behavior

CI=true nx run-many --target=test --output-style=dynamic

output-style arg is ignored (doesn't work).

This is caused by exiting early if env is on CI

if (isCI()) return false;

Expected Behavior

output-style should work within any environment.

In particular we need this to mirror lage behaviours if needed to gather data of particular task execution times.

lage output (in non verbose mode)

image

GitHub Repo

No response

Steps to Reproduce

  1. setup simple nx repo (using yarn)
  2. add at least 1 project that has test target defined
  3. run CI=true nx run-many --target=test --output-style=dynamic

Nx Report

I cannot provide report :) because of following

image

manual report:
nx 15.8.6
node 16.16
os: osx

Failure Logs

No response

Additional Information

No response

@AgentEnder AgentEnder self-assigned this Mar 10, 2023
@AgentEnder
Copy link
Member

Hey @Hotell! I'll discuss this with some other team members and get back to you.

@AgentEnder AgentEnder added type: feature scope: core core nx functionality and removed type: bug labels Mar 10, 2023
@LeoCaprile
Copy link

having the same problem, in CI I only want to render the same as I have in the terminal on local environment

local:
image

on CI:
image

doesn't even add color. :(

Any update on this?

@AgentEnder
Copy link
Member

As an update on this, the issues with nx report have been fixed, a lot of CI systems don't support dynamic terminal outputs super well when things get rewritten in the history.

@LeoCaprile
Copy link

As an update on this, the issues with nx report have been fixed, a lot of CI systems don't support dynamic terminal outputs super well when things get rewritten in the history.

Thanks!

Copy link

github-actions bot commented May 9, 2024

This issue has been automatically marked as stale because it hasn't had any activity for 6 months.
Many things may have changed within this time. The issue may have already been fixed or it may not be relevant anymore.
If at this point, this is still an issue, please respond with updated information.
It will be closed in 21 days if no further activity occurs.
Thanks for being a part of the Nx community! 🙏

@github-actions github-actions bot added the stale label May 9, 2024
@Hotell
Copy link
Contributor Author

Hotell commented May 9, 2024

a lot of CI systems don't support dynamic terminal outputs super well when things get rewritten in the history.

@AgentEnder True that but I think having possibility to output only non verbose version without the same terminal rewrites as present on local machine is a valuable feature to have ( lage has this )

@github-actions github-actions bot removed the stale label May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope: core core nx functionality type: feature
Projects
None yet
Development

No branches or pull requests

3 participants