When a team is first introduced to continuous integration they usually don’t have a formal build process. Most continuous integration servers offer powerful build orchestration tools (such as the build steps tool in Jenkins) which can make it tempting to write a build process directly in the CI server. Don’t do this.
A build process which is embedded in a CI server eventually becomes unmaintainable as it grows more complex. To avoid
this, choose a build tool (rake, psake, etc) and develop a build script which is stored and maintained in the
repository like any other source code. A well-maintained CI server should have nothing more complicated than a
rake test invocation in each job’s build command.