I was basically answering "If you're putting lots of logic into ANY CI server you're doing it wrong!". There is a separation of concern: the CI server logic is

I was basically answering "If you're putting lots of logic into ANY CI server you're doing it wrong!". There is a separation of concern: the CI server logic is a refactoring of things that are common to any project. If your project have scripts that sends email on build failure, I think you're doing something wrong. You mention at some point "orchestration scripts", this is exactly what Jenkins is supposed to provide help with: orchestration. The important thing IMO is that the boundaries of responsibilities are clearly defined between what a project does and what the orchestration does.