-
Improvement
-
Resolution: Won't Fix
-
Major
-
None
For example:
http://localhost:8080/job/frog/11/console?elapsed=01:21
...could open the console at the line that was logged 1 hour 21 minutes after the build started.
It is already possible to add anchor names into the time-stamp format, but this has several drawbacks:
- There is no way to differentiate between multiple lines with the same time-stamp.
- When opening the link, the breadcrumb bar appears on top of the target line.
- Not all lines are displayed at the /console URL, and so some anchor links have no effect unless using the /consoleFull URL.
Perhaps an offset could be used to distinguish between multiple lines with the same time-stamp, e.g.
http://localhost:8080/job/frog/11/console?elapsed=01:21
http://localhost:8080/job/frog/11/console?elapsed=01:21+1
http://localhost:8080/job/frog/11/console?elapsed=01:21+2
Raised in response to JENKINS-21171.
![qe-gate-InfraRed-ospd_qe-virsh-ospd #607 Console [Jenkins] 2017-01-26 15-44-26.png](/secure/attachment/35626/qe-gate-InfraRed-ospd_qe-virsh-ospd%20%23607%20Console%20%5BJenkins%5D%202017-01-26%2015-44-26.png)
- relates to
-
-
- Resolved
-
-
-
- Resolved
-
[JENKINS-21208] Ability to open the console at a certain line, identified by a timestamp
Steven G Brown
created issue -
Steven G Brown
made changes -
| Description |
Original:
For example: http://localhost:8080/job/frog/11/console?elapsed=01:21 ...could open the console at the line that was logged 1 hour 21 minutes after the build started. It is already possible to add anchor names into the time-stamp format, but this has several drawbacks: - There is no way to differentiate between multiple lines with the same time-stamp. - When opening the link, the breadcrumb bar appears on top of the target line. - Not all lines are displayed at the /console URL, and so some anchor links have no effect unless using the /consoleFull URL. This is confusing behaviour. An implementation using query parameters could provide a better user experience. Raised in response to |
New:
For example: http://localhost:8080/job/frog/11/console?elapsed=01:21 ...could open the console at the line that was logged 1 hour 21 minutes after the build started. It is already possible to add anchor names into the time-stamp format, but this has several drawbacks: - There is no way to differentiate between multiple lines with the same time-stamp. - When opening the link, the breadcrumb bar appears on top of the target line. - Not all lines are displayed at the /console URL, and so some anchor links have no effect unless using the /consoleFull URL. An implementation using query parameters could provide a better user experience. Raised in response to |
Steven G Brown
made changes -
| Description |
Original:
For example: http://localhost:8080/job/frog/11/console?elapsed=01:21 ...could open the console at the line that was logged 1 hour 21 minutes after the build started. It is already possible to add anchor names into the time-stamp format, but this has several drawbacks: - There is no way to differentiate between multiple lines with the same time-stamp. - When opening the link, the breadcrumb bar appears on top of the target line. - Not all lines are displayed at the /console URL, and so some anchor links have no effect unless using the /consoleFull URL. An implementation using query parameters could provide a better user experience. Raised in response to |
New:
For example: http://localhost:8080/job/frog/11/console?elapsed=01:21 ...could open the console at the line that was logged 1 hour 21 minutes after the build started. It is already possible to add anchor names into the time-stamp format, but this has several drawbacks: - There is no way to differentiate between multiple lines with the same time-stamp. - When opening the link, the breadcrumb bar appears on top of the target line. - Not all lines are displayed at the /console URL, and so some anchor links have no effect unless using the /consoleFull URL. An implementation using query parameters could provide a better user experience. Perhaps on offset could be used to distinguish between multiple lines with the same time-stamp, e.g. http://localhost:8080/job/frog/11/console?elapsed=01:21 http://localhost:8080/job/frog/11/console?elapsed=01:21+1 http://localhost:8080/job/frog/11/console?elapsed=01:21+2 Raised in response to |
Steven G Brown
made changes -
| Assignee | Original: Steven G Brown [ stevengbrown ] |
Steven G Brown
made changes -
| Description |
Original:
For example: http://localhost:8080/job/frog/11/console?elapsed=01:21 ...could open the console at the line that was logged 1 hour 21 minutes after the build started. It is already possible to add anchor names into the time-stamp format, but this has several drawbacks: - There is no way to differentiate between multiple lines with the same time-stamp. - When opening the link, the breadcrumb bar appears on top of the target line. - Not all lines are displayed at the /console URL, and so some anchor links have no effect unless using the /consoleFull URL. An implementation using query parameters could provide a better user experience. Perhaps on offset could be used to distinguish between multiple lines with the same time-stamp, e.g. http://localhost:8080/job/frog/11/console?elapsed=01:21 http://localhost:8080/job/frog/11/console?elapsed=01:21+1 http://localhost:8080/job/frog/11/console?elapsed=01:21+2 Raised in response to |
New:
For example: http://localhost:8080/job/frog/11/console?elapsed=01:21 ...could open the console at the line that was logged 1 hour 21 minutes after the build started. It is already possible to add anchor names into the time-stamp format, but this has several drawbacks: - There is no way to differentiate between multiple lines with the same time-stamp. - When opening the link, the breadcrumb bar appears on top of the target line. - Not all lines are displayed at the /console URL, and so some anchor links have no effect unless using the /consoleFull URL. An implementation using query parameters could provide a better user experience. Perhaps an offset could be used to distinguish between multiple lines with the same time-stamp, e.g. http://localhost:8080/job/frog/11/console?elapsed=01:21 http://localhost:8080/job/frog/11/console?elapsed=01:21+1 http://localhost:8080/job/frog/11/console?elapsed=01:21+2 Raised in response to |
| Workflow | Original: JNJira [ 153070 ] | New: JNJira + In-Review [ 178411 ] |
I think it may be better to implement this in the Line Numbers plugin, so I've raised some issues there: JENKINS-41283, JENKINS-41284.
Steven G Brown
added a comment - - edited I think it may be better to implement this in the Line Numbers plugin, so I've raised some issues there: JENKINS-41283 , JENKINS-41284 . There are several critical issue with line-number-plugin which rules it out as a solution for adding anchors/bookmarks to console output: is not maintained (last release in 2015) and it also has a breaking "feature" of also enabling collapsible sections, one feature that cannot be disabled.
Now regarding the original request for implementing this feature: I would point out that using timestamp itself as the anchor is a bad idea. That's because timestamper is relative to the user: it can time elapsed time or a time, time that can be UTC or browser time, making the entire URL not sharable.
Instead we should get this implemented in a simple and reliable way: just use the console line number, this one does not change and is sharable. Probably it would be easier if the timestamp text itself would become the anchor, but the anchor should be just `#linenumber`.
I really hate that I am not able to share links to specific log lines, all the other major CI systems do have this implemented.
I'm happy with this behaviour