-
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 ] |
| Link |
New:
This issue relates to |
| Link |
New:
This issue relates to |
| Attachment | New: qe-gate-InfraRed-ospd_qe-virsh-ospd #607 Console [Jenkins] 2017-01-26 15-44-26.png [ 35626 ] |
![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 #607 Console [Jenkins] 2017-01-26 15-44-26.png){kind=link}
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 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 |
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. 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 |
Steven G Brown
made changes -
| Assignee | New: Steven G Brown [ stevengbrown ] |