In addition to JENKINS-28478 ( where the pipeline shows failed even though the job is successful) , I am seeing that Build Pipeline when run from the middle of the pipeline doesn't seem to link the job to it's correct build number . However, if i run the new pipeline, the new job takes me directly to that exact build. For example, if I have a shell script running for pipeline #10's deploy QA job and it failed. Now I go back to the deploy QA job and change the configuration. If I come back to pipeline #10's deploy QA job and re-run it,it takes the new changes but the link on the build pipeline view takes me to the previous job ( the first job that was run through the pipeline). But, if I come back to the list of QA builds from outside of Build Pipeline view and check the first executed job, it is the recent one. Also on the Build pipeline view, the timestamp seems to be there from previous build even though the job is re-executed. It would be nice to update the timestamp with the most recent successful build that was re-executed rather than the one which was created when the job ran first. It would also be nice to modify it such that the link will take to the corresponding build rather than the first one. I can elaborate it more if needed. Thanks