3 ms·
The screenshot looks a bit like Chef's Automate. The config example looks like Concourse's config (http://docs.screwdriver.cd/user-guide/configuration/index#yam
by krakensden 10y ago
The screenshot looks a bit like Chef's Automate. The config example looks like Concourse's config (http://docs.screwdriver.cd/user-guide/configuration/index#yaml-configuration http://docs.screwdriver.cd/user-guide/configuration/index#ya...), but it doesn't look like they have task files.
They should write up a comparison to GoCD, Teamcity, Concourse, Jenkins, Chef Automate, etc. It can be pretty hard to evaluate these things without losing a month.
- snnn 10y agoChef cannot rollback. Chef is mainly for deployment but I think screwdriver focuses on CI. CD is not his business.
- krakensden 10y agoI mean, Chef Automate doesn't support rollback after all the usual toe dipping (https://docs.chef.io/workflow.html https://docs.chef.io/workflow.html), but that isn't terrible. Automatic rollback generally comes with a fat "but not the database" asterisk, and if you are building something general, it's a pretty reasonable decision. Screwdrivers docs all seem to mention CD, not sure why you'd say that.
- switchbak 10y agoI think in general it's becoming an intractable task to evaluate all the tools we have at our disposal. In my case, I've been using CircleCI (mostly good, but a few issues make it a non-starter), CodeFresh (awesome, but very new, still needs work), and the new Jenkins. Wanted to look at Concourse and a couple others, but just don't have the time to test drive them in any real capacity. Increasingly I think us software devs need to share our battle-won knowledge instead of just trusting the marketing blurb on a project page. Much of what I do these days just amounts to making guesses for suitable tools/projects based on heuristics and gut feelings instead of actual experience. Hopefully something like StackShare will gain in popularity, and we can start sharing our experiences more. Now time to check out Screwdriver!