EJBCA Jenkins jobs are currently not chained at all. Chaining them would provide us with benefits such as faster failures and quicker bug tracing.

Initially this should be done in the simplest way possible. Discussed scenario is:

Compile/build --> Unit tests --> System tests

The simplest way to chain jobs in Jenkins is to specify that one job should run after a successful run of another job.
Each job can in turn be chained using Jenkins pipelines, where also parallel execution of steps can be specified.