[larkost]

I have to agree with the poster. Piplines are very definitely not first-class objects: - There is no way (in the default installation) of re-running a stage without running the whole job again. - I can't see the history of a stage. - Pipelines are a plugin, that only relatively recently became a default one - They seems be the anointed new path, but live side-by-side with other branching methods like the Matrix plugin at this point.

This is all in-line with the "everything is a plugin" methodology, but in my mind that way of thinking is one of the biggest hindrances to Jenkins, second only to the lack of a real database powering it.