Are you referring to continuous integration? Cont delivery? Just stacks? If you're referring to some platforms..<p>CircleCI <a href="http://circleci.com" rel="nofollow">http://circleci.com</a> as a continuous integration and deployment platform - they automate the build, test, and deploy process.<p>LaunchDarkly <a href="http://launchdarkly.com" rel="nofollow">http://launchdarkly.com</a> if you're looking to feature flag your builds and automate rollouts.<p>Gradle <a href="http://gradle.org" rel="nofollow">http://gradle.org</a> is an open source build automation system that builds upon the concepts of Apache Ant and Apache Maven and introduces a Groovy-based domain-specific language (DSL) instead of the XML form used by Apache Maven of declaring the project configuration.
I've been using Deploybot for my hobby project and it's been sufficient. Sufficient enough that I'm upgrading to the Basic plan as my needs expand to more repositories. I do think it's lacking a per-repo payment option, though - it would be great to be able to scale your payment with your actual usage with a sort of AWS-style scaling service vs buying repository allocation in bulk.
Good ol' NPM scripts. Grunt/Gulp/Gradle are completely unnecessary for most cases.<p>As a library author, supporting every 'flavor of the month' build tool is a waste of time/effort that takes away from improving the core.<p>JSPM. Like NPM but for client-side dependencies. It has built-in transpiling, es6-module support, and can build+minify bundles and sfx bundles.