Review on kraken.ci by Louis Mechtak

I used to maintain an application which included almost 70% of our production code written in Python (mainly Flask) & NodeJS with dockerized microservices deployed over 4 different AWS accounts using multiple runners like CircleCi(CircleCI), Jenkins etc - And all was done manually for deployments as well!! It looked so much easier when we first started out but later became cumbersome due to time constraint while developing new features by getting approval from product / business lead after submitting PRs! Allowing users directly commit changes without going through dev team would really add some value here :D But what's most important now as compared back then!! We've seen huge improvment since inception regarding release management process where automation has been implemented at scale along side existing manual processes and are also able reduce turnaround times drastically!! I like how easy it was to set up our Jenkins builds for all of our projects - we only had about 15 minutes to get everything working. The UI isn't as intuitive or user friendly as some other tools out there. Some things are hard to find in the UI (e.g., setting up environment variables). We're using this tool to build code from multiple different teams at my organization and have been very happy with its performance so far.