-
Bug
-
Resolution: Duplicate
-
Major
-
-
iapetus, 1.0
tscherler the steps api is paginated with a page size of 100 - the front end code will need to change to fetch the next patch of data (cc vivek)
In Scope:
- Adjust nodes api to fetch more https://github.com/jenkinsci/blueocean-plugin/compare/raiseNodeLimitTo1000
- Test
Out of scope:
- steps api (separate ticket)
- making graph cope with loading large graphs of nodes in a paginated fashion (this needs more thinking and design).
This could be addressed with a refactoring of Karaoke I guess?
This also explains why only 100 parallel nodes are changed (in that case, it is pointless to show more, but 100 steps... you may want to show that).
It seems that we only get a limited number of steps
Using the following pipelineScript and https://github.com/scherler/blueocean-shared-library/commit/43d5620a42d7795b43bc829d694c3cae2a3c3919
@Library('test-writer') import writeTest import longLog node { stage 'fin' def xml = writeTest() sh "echo '$xml' > TEST-some.xml" step([$class: 'JUnitResultArchiver', testResults: 'TEST-*.xml']) sh 'echo `date` fin;sleep 3; echo `date` fin;' sh 'echo yeah > foo.txt' archiveArtifacts 'foo.txt' longLog(10000, false) stage 'NoSteps' }
- duplicates
-
JENKINS-39770 Pipeline visualization not rendered when there is more that 100 nodes
- Reopened
- relates to
-
JENKINS-38523 Stage listing flashes "no steps" when loading a stage for the first time (Karaoke repair)
- Closed
-
JENKINS-42781 Load more than 100 steps in a node
- Open