-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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(logging): group logging in github by task id #5318
feat(logging): group logging in github by task id #5318
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
8 Ignored Deployments
|
|
This comment was marked as off-topic.
This comment was marked as off-topic.
afaf809
to
664df8c
Compare
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
eacc2fa
to
5ef35c9
Compare
This comment was marked as off-topic.
This comment was marked as off-topic.
73813ac
to
33b87cf
Compare
The e2e windows tests are failing because it can't find the turbo binary. I want to say this is an issue because |
Similar functionality exists for other popular CI solution Teamcity: e.g. Another popular CI solution that supports something similar Gitlab: |
@weyert thanks for the note! do you mind making new issues for these if you're interested in adding support? I am on leave for a few weeks, so this PR will likely just add Github support. (You're also welcome to make a PR if you like, of course!) |
3761626
to
dc702db
Compare
# so we can prevent the `GITHUB_ACTIONS` env var from being passed down here from the top level turbo. | ||
# But as of now, this breaks our tests (and I'm not sure why). If we make that work, we can remove this | ||
# explicit locking of log order. See PR attempt here: https://github.com/vercel/turbo/pull/5324 | ||
export TURBO_LOG_ORDER=stream |
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.
This causes our integration tests (turbo_help.t
and no_args.t
, and verbosity.t
), because when clap serializes the help message from the CLI, it inlines the value of this env var. So the output diff is:
- --log-order <LOG_ORDER> Set type of task output order. Use "stream" to show output as soon as it is available. Use "grouped" to show output when a command has finished execution. Use "auto" to let turbo decide based on its own heuristics. (default auto) [env: TURBO_LOG_ORDER=] [default: auto] [possible values: auto, stream, grouped]
+ --log-order <LOG_ORDER> Set type of task output order. Use "stream" to show output as soon as it is available. Use "grouped" to show output when a command has finished execution. Use "auto" to let turbo decide based on its own heuristics. (default auto) [env: TURBO_LOG_ORDER=stream] [default: auto] [possible values: auto, stream, grouped]
We could solve this in a few ways:
- Remove the env var and figure out how to merge ci: use --env-mode=strict for tests that invoke turbo #5324
- Figure out how to make clap not inline the actual runtime value of an env var in the help message
- Change the output assertions of these tests with regex so it will match any value
Closing in favor of #5385 |
https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#grouping-log-lines