Stage View: left hand side "Builds" list out of sync

Using Jenkins Ask a question
1

Hello community,

I’ve noticed that recently the small “Builds” list on the left hand side of Stage View got out of sync with what was happening in SV like in the example screenshot below.

Has anyone noticed this as well or is that an undocumented feature of our specific installation? Or perhaps its a know (and fixed?) bug?

grafik
grafik1408×1251 106 KB

Jenkins: 2.492.1
OS: Linux - 4.15.0-213-generic
Java: 17.0.14 - Eclipse Adoptium (OpenJDK 64-Bit Server VM)

active-directory:2.39
ant:513.vde9e7b_a_0da_0f
antisamy-markup-formatter:162.v0e6ec0fcfcf6
apache-httpcomponents-client-4-api:4.5.14-269.vfa_2321039a_83
apache-httpcomponents-client-5-api:5.4-136.v5a_21779c63f8
asm-api:9.7.1-97.v4cc844130d97
authentication-tokens:1.119.v50285141b_7e1
bootstrap5-api:5.3.3-2
bouncycastle-api:2.30.1.80-256.vf98926042a_9b_
branch-api:2.1214.v3f652804588d
build-pipeline-plugin:2.0.2
build-timeout:1.36
built-on-column:1.5
caffeine-api:3.2.0-161.v691ef352cee1
checks-api:2.2.3
cloud-stats:377.vd8a_6c953e98e
cloudbees-disk-usage-simple:232.v713eeed2e1f4
cloudbees-folder:6.982.vf165a_16c9507
command-launcher:118.v72741845c17a_
commons-compress-api:1.27.1-2
commons-lang3-api:3.17.0-84.vb_b_938040b_078
commons-text-api:1.13.0-153.v91dcd89e2a_22
conditional-buildstep:1.5.0
config-file-provider:982.vb_a_e458a_37021
copyartifact:765.v0357cc6e6eb_3
credentials:1408.va_622a_b_f5b_1b_1
credentials-binding:687.v619cb_15e923f
dashboard-view:2.528.v3470c02b_d7c9
data-tables-api:2.2.2-1
disable-job-button:1.v9db_352414f90
display-url-api:2.209.v582ed814ff2f
docker-commons:445.v6b_646c962a_94
docker-custom-build-environment:1.7.3
docker-java-api:3.4.1-96.v77147a_de67f8
docker-plugin:1.9.0
docker-slaves:1.0.7
docker-workflow:596.v3e6972b_46b_e2
durable-task:581.v299a_5609d767
echarts-api:5.5.1-6
eddsa-api:0.3.0-4.v84c6f0f4969e
email-ext:1876.v28d8d38315b_d
emailext-template:224.va_f6a_ecd5d46e
embeddable-build-status:548.v5653c6e28c41
envinject:2.926.v69c9b_3896a_96
envinject-api:1.235.va_14c74f8f487
extended-read-permission:61.vf24570ff3b_e9
external-monitor-job:221.v35059272565b_
external-workspace-manager:1.3.1
font-awesome-api:6.7.2-1
generic-webhook-trigger:2.3.1
git:5.7.0
git-changelog:3.43
git-client:6.1.2
git-parameter:0.11.0
git-server:126.v0d945d8d2b_39
gitea:238.v626a_cf5e1940
github:1.42.0
github-api:1.321-478.vc9ce627ce001
github-branch-source:1810.v913311241fa_9
github-pullrequest:0.7.2
gson-api:2.12.1-113.v347686d6729f
handy-uri-templates-2-api:2.1.8-30.v7e777411b_148
htmlpublisher:1.37
http-post:1.2
influxdb:4.0
instance-identity:201.vd2a_b_5a_468a_a_6
ionicons-api:74.v93d5eb_813d5f
jackson2-api:2.17.0-389.va_5c7e45cd806
jakarta-activation-api:2.1.3-2
jakarta-mail-api:2.1.3-2
javadoc:310.v032f3f16b_0f8
javax-activation-api:1.2.0-8
javax-mail-api:1.6.2-11
jaxb:2.3.9-1
jdk-tool:83.v417146707a_3d
jenkins-multijob-plugin:662.vd2e0001f6b_b_d
jersey2-api:2.45-154.v4ded3dc34f81
jjwt-api:0.11.5-120.v0268cf544b_89
jnr-posix-api:3.1.20-125.vb_6ec4b_21b_15e
job-restrictions:212.vc34d63a_6704b_
joda-time-api:2.13.1-115.va_6b_5f8efb_1d8
jquery:1.12.4-3
jquery3-api:3.7.1-3
jsch:0.2.16-86.v42e010d9484b_
json-api:20250107-125.v28b_a_ffa_eb_f01
json-path-api:2.9.0-148.v22a_7ffe323ce
junit:1317.v5b_35d792b_06a_
ldap:776.vddf3e325103b_
lockable-resources:1349.v8b_ccb_c5487f7
mailer:489.vd4b_25144138f
mantis:0.26
mapdb-api:1.0.9-40.v58107308b_7a_7
matrix-auth:3.2.4
matrix-project:845.vffd7fa_f27555
maven-plugin:3.25
metrics:4.2.21-461.v881e35d8fa_b_a_
mina-sshd-api-common:2.14.0-143.v2b_362fc39576
mina-sshd-api-core:2.14.0-143.v2b_362fc39576
msbuild:1.36
nodejs:1.6.4
okhttp-api:4.11.0-183.va_87fc7a_89810
oss-symbols-api:296.v4981240eeb_1a_
pam-auth:1.11
parameterized-trigger:840.v3c7d4a_a_5e6c7
pipeline-build-step:555.v589d5c24a_3d6
pipeline-github-lib:65.v203688e7727e
pipeline-graph-analysis:231.v56354571a_da_0
pipeline-groovy-lib:752.vdddedf804e72
pipeline-input-step:513.v7eb_fe7e2c0fc
pipeline-milestone-step:126.vd50e283c65e7
pipeline-model-api:2.2221.vc657003fb_d93
pipeline-model-definition:2.2221.vc657003fb_d93
pipeline-model-extensions:2.2221.vc657003fb_d93
pipeline-rest-api:2.37
pipeline-stage-step:322.vecffa_99f371c
pipeline-stage-tags-metadata:2.2221.vc657003fb_d93
pipeline-stage-view:2.37
pipeline-utility-steps:2.19.0
plain-credentials:183.va_de8f1dd5a_2b_
plugin-util-api:6.0.0
powershell:2.3
prometheus:819.v50953a_c560dd
publish-over:0.22
publish-over-ftp:248.v1487ff759c7a_
resource-disposer:0.25
run-condition:243.v3c3f94e46a_8b_
scm-api:703.v72ff4b_259600
script-security:1373.vb_b_4a_a_c26fa_00
snakeyaml-api:2.3-123.v13484c65210a_
ssh-agent:376.v8933585c69d3
ssh-credentials:349.vb_8b_6b_9709f5b_
ssh-slaves:3.1031.v72c6b_883b_869
sshd:3.353.v2b_d33c46e970
structs:343.vdcf37b_a_c81d5
subversion:1287.vd2d507146906
timestamper:1.28
token-macro:444.v52de7e9c573d
trilead-api:2.147.vb_73cc728a_32e
variant:70.va_d9f17f859e0
versioncolumn:320.v6b_b_814ca_01f7
workflow-aggregator:600.vb_57cdd26fdd7
workflow-api:1363.v03f731255494
workflow-basic-steps:1079.vce64b_a_929c5a_
workflow-cps:4018.vf02e01888da_f
workflow-durable-task-step:1405.v1fcd4a_d00096
workflow-job:1505.vea_4b_20a_4a_495
workflow-multibranch:800.v5f0a_a_660950e
workflow-scm-step:437.v05a_f66b_e5ef8
workflow-step-api:686.v603d058a_e148
workflow-support:946.v2a_79d8a_4b_e14
ws-cleanup:0.48
Jenkins setup:
2

I assume you’re talking about the left side where the lastest build is #1024 while stage view shows that the latest build is #1032
Stage View has nothing to do with the left sidepanel. The left sidepanel with the Builds is a core feature of Jenkins. Might be a bug though I’ve never seen that before

3

yep, it’s that contradiction that surprised me. I asked my IT department and they said they’ve never seen it before. Maybe that indicates how often they use it - or maybe it only affects my jobs (as I’m seeing it almost any time now)

4

hmm, that part of the build history is loaded asynchronously via javascript. And that part was reimplemented in 2.479.1
Do you see all builds when you click on the Expand button

image
image443×139 2.44 KB

This should get you to the buildTimeTrend page

5

yep, that shows the news jobs!

6

Not sure if it adds anything new - but here’s another screenshot which shows 'em severely being out of sync.

grafik
grafik1282×475 43.4 KB

7

But on that screenshot everything is good. On both sides the first build to be shown is #12.
If you mean that the lines are not the same height and start at the same position from the top, then this has never been the case. What is shown above the stage view depends on what plugins you have installed. Or if you add a lengthy description to the job, then the stage view will also shift down.
Or are you talking about the bug mentioned here: https://issues.jenkins.io/browse/JENKINS-75271

8

Except that SV shows all jobs as completed while a lot of them still seem to be running (on the left)

9

And who is correct? Stage view or the Build History on the left?
Maybe there is some javascript bug that prevents that the build history gets updated properly. You could check with the browser console if there are errors reported.

10

SV is correct. I’m afk now, but when I see t again I’ll check dev console!

11

I just saw it again and then switched to devconsole which has this:

No "data-stageId" on stage. 9 [pipeline-staged.js:173:24](http://***/plugin/pipeline-stage-view/jsmodules/src/main/js/view/pipeline-staged.js)

12

Does that happen directly after loading the page?
That message comes from stage-view and looks just like a warning.

In the browser console, switch to Network tab. There you should see requests with ajax?search= When you click that it the url should go to <job_url>/buildHistory/ajax?search=
As response it should send basically the content of the history widget.
And it should be called every 5 seconds.
If that is called regularly it would mean that the problem is in the Java code somewhere.

13

it doesn’t happen on loading, but when I click the “Build” button. And as long as it is building, the message comes up repeatedly.

14

Markus, how are such bugs dealt with? Should I report it somewhere - or have you possible done that or…? (Sorry for asking - never needed to do this as IT handles Jenkins)

15

The message

No "data-stageId" on stage. 9 [pipeline-staged.js:173:24](http://***/plugin/pipeline-stage-view/jsmodules/src/main/js/view/pipeline-staged.js)

is not the problem I think. This looks just like a warning from stage-view plugin. And that it comes regularly while builds are running is also no surprise.
But the behaviour that the build-history in the left sidepanel is not updated might be a bug in core, although hard to track, I looked a bit in the code but couldn’t find anything that would explain the problem.
See Issue Reporting how to report a bug