Bazooka runs every build as a sequence of steps or phases regardless of the language it uses. Every phase consits of running one or more commands. Bazooka then uses the return codes of running theses commands to decide whether to continue or abot the build, and what status to attach to it (success, failure, ...)
Language specific plugins can and should define what commands to run in every phase.
for example, the Java plugin defaults to running mvn install in the install phase and mvn test in the script phase if your project has a pom.xml file.
You can still override any of the default commands to run in any phase in the .bazooka.yml file by setting the phase key.
The build phases are :
before_installinstallbefore_scriptscriptafter_successafter_failureafter_script
In a before_install step, you can install additional dependencies required by your project, Ubuntu packages for instance, or custom services, downloaded and installed from the internet.
In this step, you will install any dependencies required. For instance, you will run bundle install for a ruby application
Run any command necessary before running your build script.
Run a script that effectively runs the build or the tests. For instance, in a ruby application, you would run bundle exec rake
after_success commands are executed when the script commands are successful. A common task for after_success is to generate documentation, or to upload a build artifact to S3 for later use. You can also use this step to deploy your code to your staging or production servers.
after_failure commands are executed when any of the script commands failed. after_failure can be used in similar ways to after_success, for example to upload any log files that could help debugging a failure to S3.
after_script commands are always executed at the end of the build, regardless of the result of the previous commands.
The build status of a bazooka build consists of 3 states:
If no errors were raised during the install and script phases, the build gets marked as succeeded
When any of the steps in the before_install, install or before_script stages fails with a non-zero exit code, the build will be marked as errored.
When any of the steps in the script stage fails with a non-zero exit code, the build will be marked as failed.