-
Bug
-
Resolution: Not A Defect
-
Minor
-
None
from cliffmeyers:
Hitting the /runs REST API for a Pipeline shows all the job runs, including those that probably should be in the /queue. The status of all jobs is "RUNNING" which also feels a bit misleading.
from vivek
What needs to happen is that if a build item is in queue, should not be returned. We should not be mixing run object with queue because they are vastly different. There is already an API /pipeline/:id/activities Ivan implemented to give all runs and items in queue, so if this is what you look for you can use that.
- is related to
-
-
- Closed
-
[JENKINS-37338] Pipeline scripts that should appear in /queue are returned in /runs API
| Epic Link | New: JENKINS-35759 [ 171771 ] |
| Link |
New:
This issue is related to |
I think the missing piece is showing the activity of Jenkins in the not-yet-implemented GUI, this would make it clear...
otherwise, if there was a way we could enquire as to what "parts" of a pipeline are doing... we could report more intelligently why it is waiting when it is in the RUNNING state...
IN a sense we don't really want "Queued" anyway - it is an artifact of Jenkins internals that we don't always want to expose.
What we may want to expose is that their build is in a bad way because of exahusted executors or mis configuration - that is really what it is about.
Summary: for pipeline this is actually "correct" behavior, as there is no queue on a per pipeline basis. Much more work is needed to show what parts of it are in a piepline and where it is blocked.
| Sprint | New: 1.0-beta-1 [ 96 ] |
| Rank | New: Ranked lower |
| Priority | Original: Major [ 3 ] | New: Minor [ 4 ] |
| Rank | New: Ranked higher |
cliffmeyers
Based on what I discovered after experimenting with pipeline/nodes and its behavior w.r.t being in queue and its state running as well as being in queue, I think our api implementation tries to do such re-arrangment of pipeline run state is recipe for more confusion and errors. See my last mail. Fact that a pipeline is in RUNNING state is truth and should be represented that way because its indeed running. At the same time, based on how the script is, part of it might be in queue. I am not really sure what else can we do really.