Manually kicked job does not show up executed in pipeline

[Abhiram Dwivedi]

I have a delivery pipeline as:

 ==========                  =========                 =========

|     JOB 1      |    ====>   |     JOB 2    | ====>   |    JOB 3     |

 ==========                  =========                 =========

JOB1 Parameters: PARAM1

JOB2 Parameters: PARAM1, PARAM2

JOB3 : No parameters

I kicked off JOB1 from pipeline, and it shows JOB2 as ready to be kicked. I manually started JOB2 (by going to the job, and not from pipeline), providing additional PARAM2. I expect the pipeline to show JOB3 as ready to be kicked. But the pipeline still shows that JOB2 needs to be kicked.

Is this a bug, or am I missing something?

[Substance586]

In my experience manually kicking off a job from that job's project page never shows up on a delivery pipeline view, even if it's the next job to be run on the pipeline.  The delivery pipeline view acts as a dashboard that expects all jobs to be run from it, which is not a bad way of interacting with Jenkins jobs IMO especially when you have manual jobs and rebuild plugin installed.  

However the handling of manual jobs has long been a sore point, dare I say thee #1 sore point, of this plugin.  I really, really wish it would prompt you for parameters when you initiate a manual job from the pipeline view.  

A possible solution for you however would be to open up the job's configuration page, set the default value(s) of the parameter(s) you need to enter, save it, go back to the pipeline view and manually trigger the job from there.  I think that will get you past your issue.  Good luck!