<p>Jenkins stage view is in fact showing that the jobs have ended.  More specifically, the jobs have failed, as indicated by the &quot;failed&quot; in the bottom-right corner of the stage which failed.</p>

CC BY-SA 4.0
2021-09-16T07:56:10.540Z
Yes, but notice the progress bar under the header 13min28s - this seems to indicate that something is still being worked on. (Or maybe I misinterpret, but usually a completed job does not show such indicators)
MBaas
CC BY-SA 4.0
2021-09-16T16:05:19.693Z
@MBaas that's not a progress bar.  It's showing what chunk of the total execution time that stage consumes.  Compare it to the bars for the next two stages to the right, which show that those stages consumed smaller chunks of time towards the end of the pipeline execution.
jayhendren
CC BY-SA 4.0
2021-09-17T01:55:51.080Z
@jayhendren, perhaps add the progress elaboration to your answer zto make it complete.
Ian W
CC BY-SA 4.0
2021-09-17T06:09:27.657Z
Thanks! I misinterpreted that :(
MBaas
CC BY-SA 4.0
2021-09-15T15:56:45.473Z
2021-09-15T15:56:45.473Z
jayhendren
<p>I am using Jenkins' remote API (XML &amp; JSON) to submit Jobs, run them &amp; retrieve the logs. When observing the jobs in Stage View, I noticed that (following a change in my &quot;submission function&quot;) the jobs are shown as &quot;processing&quot; while they have completed:
<a href="https://i.sstatic.net/vAsre.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/vAsre.png" alt="enter image description here" /></a></p>
<p>How can one deal with such issues? (I'm not a DevOps person, I am developer that happened to be chosen as the one to deal with Jenkins. I had no courses or so, just received a sample script and googled the rest)</p>
<p>Ah, I mentioned that change in my submission function: not knowing anything, when my submitted jobs were rejected (because a job with that name already existed), I created unique names for my jobs. This created lots of workspaces that IT wasn't happy with, so I learned how I could update existing jobs and changed my code accordingly. That's when I started seeing neverending jobs...</p>

<jenkins><jenkins-pipeline>
Why does Jenkins' Stage View not show my jobs as ending?
MBaas
# Why does Jenkins' Stage View not show my jobs as ending?

(Asked by: username_0 on 2021-09-15)

I am using Jenkins' remote API (XML & JSON) to submit Jobs, run them & retrieve the logs. When observing the jobs in Stage View, I noticed that (following a change in my "submission function") the jobs are shown as "processing" while they have completed:
[![enter image description here](https://i.sstatic.net/vAsre.png)](https://i.sstatic.net/vAsre.png)

How can one deal with such issues? (I'm not a DevOps person, I am developer that happened to be chosen as the one to deal with Jenkins. I had no courses or so, just received a sample script and googled the rest)

Ah, I mentioned that change in my submission function: not knowing anything, when my submitted jobs were rejected (because a job with that name already existed), I created unique names for my jobs. This created lots of workspaces that IT wasn't happy with, so I learned how I could update existing jobs and changed my code accordingly. That's when I started seeing neverending jobs...

**Tags:** jenkins, jenkins-pipeline


---

## 1 answers

### Answer by username_1 on 2021-09-15. Score: 1 | Accepted answer

Jenkins stage view is in fact showing that the jobs have ended. More specifically, the jobs have failed, as indicated by the "failed" in the bottom-right corner of the stage which failed.

> **Comments:**
> **username_0**: Yes, but notice the progress bar under the header 13min28s - this seems to indicate that something is still being worked on. (Or maybe I misinterpret, but usually a completed job does not show such indicators)  
> **username_1**: @username_0 that's not a progress bar.  It's showing what chunk of the total execution time that stage consumes.  Compare it to the bars for the next two stages to the right, which show that those stages consumed smaller chunks of time towards the end of the pipeline execution.  
> **username_2**: @username_1, perhaps add the progress elaboration to your answer zto make it complete.  
> **username_0**: Thanks! I misinterpreted that :(  

---

