Have to fix a bug first, that I remember mentioned somewhere. Queued job do not have an id.

To reproduce: Remove all executers from your master jenkins and start a job

Then try the activity page of the project, refresh the page and you will see

They don't have a run ID, but they do have a queueId. The queueId will be on the run too once it is created.

ok I will look into it

I did a deeper look into this. The problem is the following:

Currently we only see "queued" jobs through the sse, but we cannot see them in details unless they have received a jobId. That means as well that this jobs are not appearing in the runs array e.g. http://localhost:8080/jenkins/blue/rest/organizations/jenkins/pipelines/bomb/runs/ which explains that you only see them when triggered by sse. They appear in http://localhost:8080/jenkins/blue/rest/organizations/jenkins/pipelines/bomb/queue/

The question now what is the "right thing" to do. If we want to be able to see queued item, we would need to "merge" the "runs" with the "queue" array in the redux runs and distinct them to fetch in the detail view against the queue storage.

However classic Jenkins currently does not provide a link for queue item which IMO makes sense, since the item has no information other then the time when it got in the queue

jamesdumay WDYT the quick fix is to disable the link to the detail while queued, or should I go the merge queue/runs route?

Hey tscherler, see JENKINS-36209. These issue seems very close in nature. See the comments there and the question I asked to vivek.

tfennelly Thank you buddy. Until the other is not fixed this.onHold()

imeredith this kinda looks like the one we spoke about last week?