With multiple projects that all build after one another, you can quickly lose sight of dependencies between projects. We have a build project, unit tests, E2E tests, database tests, deployment, and many more. Who knows what else. Well, we have got a plugin for that. Install the Build Pipeline plugin (https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin) from the plugin manager. After that, create a new view and you will find a new view type, Build Pipeline View. Pick this type, give it a name, for example, CSharp Web Shop Pipeline, and pick the initial job. The initial job is the first project that is started and which will trigger other builds.
For example, I have set up my builds so that deployment (which is just an empty project) is triggered after the E2E tests (which we will fix shortly), which is triggered after database testing, which is triggered...
