Display information based off the previous run#626
Conversation
Signed-off-by: lewisbirks <22620804+lewisbirks@users.noreply.github.com>
Signed-off-by: lewisbirks <22620804+lewisbirks@users.noreply.github.com>
Signed-off-by: lewisbirks <22620804+lewisbirks@users.noreply.github.com>
Signed-off-by: lewisbirks <22620804+lewisbirks@users.noreply.github.com>
Signed-off-by: lewisbirks <22620804+lewisbirks@users.noreply.github.com>
timja
left a comment
There was a problem hiding this comment.
Some minor feedback, looks great though
src/main/frontend/common/tree-api.ts
Outdated
| ); | ||
| }; | ||
|
|
||
| const onPipelineComplete = () => undefined; |
There was a problem hiding this comment.
this could be defined before the if statement so you don't repeat it on L#57
There was a problem hiding this comment.
makes sense for now as they are the same, eventually they might differ, but we can deal with that then
| const ONE_MONTH_MS: number = 30 * ONE_DAY_MS; | ||
| const ONE_YEAR_MS: number = 365 * ONE_DAY_MS; | ||
|
|
||
| // TODO: 16/04/2025 How to support i18n like the methods this was copied from |
There was a problem hiding this comment.
does this need resolving (or a follow up)?
There was a problem hiding this comment.
Still thinking how to do this, potentially a follow up unless you have any ideas. though this PR is getting rather large
There was a problem hiding this comment.
There's this function: https://github.com/jenkinsci/jenkins/blob/4d2698f254b039bedd7b8f5af89e0c25b3b88b1e/src/main/js/util/i18n.js#L1
I've never used it but I think it was introduced for the setup wizard.
The normal pattern that a bunch of places use is to copy the messages from java / jelly using data- attributes on an element and then JavaScript just reading the data attributes.
There was a problem hiding this comment.
Follow up would be fine if we create an issue
Define complete action once Use braces on throws Signed-off-by: lewisbirks <22620804+lewisbirks@users.noreply.github.com>
Signed-off-by: lewisbirks <22620804+lewisbirks@users.noreply.github.com>
|
good to go @janfaracik? |
|
Just fixing a small animation issue, will be good once thats fixed |
|
Good to go 🚀 |
* Calculate the percentage complete based off the previous run * Add very rough progress ring icon * Add animations for icons * Init * Move the timing string generation to the frontend * Rough skeletons * Spooky scary skeletons * Align makeTimeSpanString with what is in core * Mostly remove completePercent from the API (defaults to 0) Signed-off-by: lewisbirks <22620804+lewisbirks@users.noreply.github.com> * Tidy * Update status-icon.tsx * Cleanup Signed-off-by: lewisbirks <22620804+lewisbirks@users.noreply.github.com> * Restore match * Estimate stage completion percentage Signed-off-by: lewisbirks <22620804+lewisbirks@users.noreply.github.com> * Linting Signed-off-by: lewisbirks <22620804+lewisbirks@users.noreply.github.com> * Pull out API polling * Tidy up * Update merger.spec.ts * Timings -> timings + tsx -> ts Signed-off-by: lewisbirks <22620804+lewisbirks@users.noreply.github.com> * Tidy up * Undo unneeded java changes Signed-off-by: lewisbirks <22620804+lewisbirks@users.noreply.github.com> * Pull URL from element * More reversions Signed-off-by: lewisbirks <22620804+lewisbirks@users.noreply.github.com> * Update nodes.tsx * Rename stuff * Move files * Add test for run-estimator * Trigger Build * Rename complete * Update ConsoleLogCard.spec.tsx * Populate map at initialisation Define complete action once Use braces on throws Signed-off-by: lewisbirks <22620804+lewisbirks@users.noreply.github.com> * Add click state to status symbols * Add guard for previous build url Signed-off-by: lewisbirks <22620804+lewisbirks@users.noreply.github.com> * Drop skeletons if stages differ, simplify * Fix animation when switching between clickable and not clickable --------- Signed-off-by: lewisbirks <22620804+lewisbirks@users.noreply.github.com> Co-authored-by: Jan Faracik <43062514+janfaracik@users.noreply.github.com>

This PR revamps the graph view to:
We'd like to extend this to the console view eventually - but that'll require more work in an already big PR
Testing done
Fixes #619
Submitter checklist