-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
feat(core): improve checks for process.env.CI #22694
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit f063626. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 1 targetSent with 💌 from NxCloud. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR! I think we can do this in a bit more agnostic way.
Rather than adding an additional check for woodpecker specifically, can you update the earlier check from process.env.CI === 'true'
to (process.env.CI && process.env.CI !== 'false')
a41b94a
to
23d2f26
Compare
@AgentEnder thank you for the review!
done 👍 |
22106e3
to
34688ae
Compare
ab38675
to
851acc5
Compare
23836b1
to
a3b0874
Compare
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Current Behavior
Today, nx does not disable the output styling and WoodpeckerCI doesn't go well with it, This requires us to manually add "output-style=stream" to every nx command, which solves the issue but I understand that we could have a woodpecker check to isCI function as well
reference:
https://woodpecker-ci.org/docs/usage/environment#built-in-environment-variables
Expected Behavior
Disable styling in nx command outputs when running in WoodpeckerCI
Related Issue(s)
I haven't found a related issue, but this PR came as a suggestion in this discord thread: https://discord.com/channels/1143497901675401286/1225808236104646706
@ edit
the title is "feat(core): add WoodpeckerCI to isCI check" but the check also applies to other CI vendors that set process.env.CI to a non-empty string
@ edit2
I've improved the PR title with feat(core): improve checks for process.env.CI since it now covers all CI players that dont'set process.env.CI directly to "true" but to other values instead