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

Please add time stamps. #17491

Closed
RokeJulianLockhart opened this issue Jun 30, 2024 · 3 comments
Closed

Please add time stamps. #17491

RokeJulianLockhart opened this issue Jun 30, 2024 · 3 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@RokeJulianLockhart
Copy link

RokeJulianLockhart commented Jun 30, 2024

Description of the new feature/enhancement

I want time stamps in the terminal for every command (although some would prefer for every line number, potentially).

I envision it like gitlab.com/gitlab-org/gitlab/-/blob/72e14aa6bb97c6e10870812ac9b521d41b8f890b/doc/ci/yaml/ci_job_log_timestamps.md#example-configuration-and-output depicts:

Example configuration and output

Example pipeline configuration with FF_TIMESTAMPS enabled:

variables:
  FF_TIMESTAMPS: true

Example log output with FF_TIMESTAMPS enabled:

Timestamps for each log line

...which happens to depict how this feature would work well with #17490 (comment).

Proposed technical implementation details (optional)

gitlab.com/gitlab-org/gitlab/-/issues/463391 contains most of the useful discussions regarding implementation.

@RokeJulianLockhart RokeJulianLockhart added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jun 30, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jun 30, 2024
@RokeJulianLockhart
Copy link
Author

RokeJulianLockhart commented Jun 30, 2024

#17491 (comment)

This might be a duplicate of #9331 (comment), in retrospect (although I think I've phrased it better if so).

@carlos-zamora
Copy link
Member

Thanks for filing! Marking this as a /dup of #9331.

Copy link
Contributor

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@microsoft-github-policy-service microsoft-github-policy-service bot added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jul 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants