Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
None
-
-
1.0-m10, 1.0-m11, 1.0-m12, 1.0-pre-beta-1
Description
Somewhere along the lines we broke queued items appearing on the activity tab. vivek is working on a fix to make this possible and will advise on this ticket when JENKINS-36208 is completed.
In Scope
- Ensure that queued items appear on the activity
- New items appear in the activity without reloading (SSE)
- Test case to capture this in future
Attachments
Issue Links
- blocks
-
JENKINS-36643 Developer viewing a queued pipeline is given a better indication of the state
-
- Resolved
-
- is blocked by
-
-
- Closed
-
- is blocking
-
-
- Resolved
-
- is related to
-
-
- Resolved
-
Activity
vivek wouldn't the performance problem be solved by the cache lookup we discussed?
jdumay Yes only for the items in the queue. We were discussing here all run objects to be searchable using queue id - that is stop using build id for run api. thats expensive, in memory caching works for small sized objects, here we are talking about cache that spans across all pipelines and their builds.
There must be some way we can get a feed of the equivalent info for the agent activity in classic - if this was available then maybe this can be correlated with any in progress things. As it is, information seems to go into a black hole and we have a broken user experience.
This will result in many duplicate build requests when people manually kick off a build.
OK... 2 rest API calls it is then it seems .... user friendly and performant vs one API call