An (almost) free Continuous {Integration|Deployment|Delivery} Environment

  • Of course a hosted version control system and a build server which executes my unit and integration tests after every commit.
  • Automated deployment to a test environment after every commit.
  • Automated tests against this deployment after every commit. I’ve seen it in so many projects that a deployment was „successful“ but nobody cared if the app is really running.
  • An easy way to release my application and deploy it to the production environment with a click of a button. This step should of course include all the pre and post tests like in the test environment.
  • A code quality tool that generates reports after every commit.
  • Monitoring of all environments. From my experiences the chances that a test environment is monitored are really low for projects on which you don’t work constantly. So the chances that your test environment is down when you start on your next feature are high. And even better: nobody knows who broke it accidentally weeks ago…
  • Setting up new environments with a click of a button for instance via Puppet or Chef. I don’t need more environments in the near future. Also: janedoe is a dropwizard app including all configuration so all I need for a new environment is a Java Runtime and some environment variables. Should be easy to set up manually.

Runtime Environment

Source Code Management

Automated Workflow

failed Codeship build



Code Quality Management





developer at

Love podcasts or audiobooks? Learn on the go with our new app.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Florian Hirsch

Florian Hirsch

developer at

More from Medium

Continuous Deployment in Client-Server Architecture

An Effective Incident Escalation Process of Sendoso

How to Multistream with Linode WIP

BATS (Bash Automated Testing System)