Build Pipeline Plugin is one of my favorite Jenkins plugins. It allows you to build a pipeline out of several jobs by defining upstream and downstream jobs. This way you can create a process consisting of multiple steps from running unit tests, various code quality tools (lint, mess detector, copy paste detector etc), BDD tests, through deployment to different environments (integration, functional test, production).
This allows you to manage whole journey of an application from committing to version control (Git, SVN etc) to deployment on production servers. In addition, the Build Pipeline Plugin also represents this journey in a very nice visual way.
The only big issue I have with this plugin relates to manually triggered parametrized jobs. The problem is, when you have a parametrized job which requires a manual submission (deployment to staging or production certainly does), it should ask you to manually enter the required parameters when you trigger the job from the pipeline view. This doesn’t happen and it triggers the build without any parameters.
This is quite annoying and has forced me to remove jobs like this from the pipeline for now (until the plugin is updated to support this very important feature…).