Details
-
Type:
Story
-
Status: Resolved (View Workflow)
-
Priority:
Blocker
-
Resolution: Fixed
-
Component/s: sse-gateway-plugin
-
Labels:None
-
Similar Issues:
-
Epic Link:
-
Sprint:1.0-m10
Description
The default bare-bones thin events are sometimes not enough e.g. Blue Ocean needs some additional info about Job events, such as whether or not it's a muti-branch job, the Jenkins org the job belongs to etc.
At the moment, Blue Ocean is fudging this by parsing the job url and making a few assumptions. This is dodgy and we should fix it before we go too far. Allowing BO to define an @Extension point impl that adds the few extra fields it needs would be good because then it would not longer need to make any assumptions.
Attachments
Issue Links
- is related to
-
JENKINS-36261 Lack of feedback that a build has been requested
-
- Resolved
-
Activity
Tom FENNELLY is that why SSE is not working at the moment? (well at least none I can see works anymore). If I launch a multibranch job (either via the button, or via classic) - no events are picked up.
No toast pops up etc?
Michael Neale I have verified that the current UI issue for multi-branch job states not updating is related to this issue. SSE itself is working insofar as the events are being pushed out to the client. The issue is in how they are being interpreted for multi-branch (normal pipeline job works fine for me).
yes, have confirmed it is not there in non multibranch, so does indeed seem related to this exact issue with upgrading the branch-api.
Well spotted.
After updating the pipeline deps in Blue Ocean I can see that the branch-api has changed the job URL structure, which breaks the current event stuff, making it critical that we fix this issue.