Review on SBuild by Dexter Rasberry

The way sbuild handles dependencies between packages, sub-projects etc has been very efficient so far! It also does not have any problem with handling parallel builds which was my main pain point while using Maven earlier (I use it to deploy micro services). I can't comment much about how easy/difficult this tool would be if you're new into code deployment or CI pipeline but as per me having used both Jenkins(Maven) & CircleCI, setting up an entire CI workflow including tests could just take 2 mins - maybe even less time than that considering all of them combined together might cost more :) Definitely give it try before jumping straight away to something else! You should definitely check out the documentation first otherwise your troubles will start increasing after every commit :P Also checkout some video tutorials online regarding their features like Pipeline configuration options available under advanced section along with examples. Setting things right from scratch takes lot longer then one expects when implementing such kind of tools for continuous integration purpose especially at early stages ;) The fact that I can write my own custom rules to control when each stage of compilation should execute, which allows me more flexibility than some other similar tools out there (eclipse's Ant). It doesn't have any GUI so it requires you learn how to use sbt from scratch if your not familiar with scala or SBT already. If this issue has been solved then its great otherwise just stick with maven as they support many different languages/frameworks much better!