Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Screwdriver: Yahoo's Continuous Delivery Build System for Dynamic Infrastructure

yahooeng.tumblr.com

Post reply on HN
Print view View original

51–60 of 62 posts

Re: Screwdriver: Yahoo's Continuous Delivery Build System for Dynamic Infrastructure

#51

Post by specialist »

perlgeek wrote: post #42
TheAceOfHearts wrote: post #37

Although Yahoo doesn't seem to be doing very well recently, they've done lots of great engineering. I recently looked through the organization's Github [0] and discovered a few nice packages. I'd happily pay for a good managed CD build system capable of handling projects / products with multiple dependencies. Right now I use CircleCI along with a bunch of scripts, and it works, but it's not great. One problem with ex…

Fwiw https://gocd.io/ handles pipelines (or graphs of multiple piplines) with several git repos just fine. That's on-premise, but not hard to run on your own. There's Snap CI, which is by ThoughtWorks (just as Go CD), and that's in the cloud. I don't know if they use the same code base, but it might be worth investigating if they can deal with multiple repos in a sensible way.

We just switched to GoCD. And here I thought Jenkins sucked.

I've never missed simple shell scripts, builds triggered by commits, tailing logs so much. Being closer to the metal. Back then, I had no idea the obvious solution was called "continuous integration".

GoCD has a pretty dash board though. So I guess that's progress.

Re: Screwdriver: Yahoo's Continuous Delivery Build System for Dynamic Infrastructure

#52

Post by mariusmg »

specialist wrote: post #51
perlgeek wrote: post #42

Earlier quoted context omitted.

Fwiw https://gocd.io/ handles pipelines (or graphs of multiple piplines) with several git repos just fine. That's on-premise, but not hard to run on your own. There's Snap CI, which is by ThoughtWorks (just as Go CD), and that's in the cloud. I don't know if they use the same code base, but it might be worth investigating if they can deal with multiple repos in a sensible way.

We just switched to GoCD. And here I thought Jenkins sucked. I've never missed simple shell scripts, builds triggered by commits, tailing logs so much. Being closer to the metal. Back then, I had no idea the obvious solution was called "continuous integration". GoCD has a pretty dash board though. So I guess that's progress.

>So I guess that's progress.

No it's not, because scripts are better to debug the problem when (invariably) all goes to shit.

Re: Screwdriver: Yahoo's Continuous Delivery Build System for Dynamic Infrastructure

#53

Post by bpp »

perlgeek wrote: post #42
TheAceOfHearts wrote: post #37

Although Yahoo doesn't seem to be doing very well recently, they've done lots of great engineering. I recently looked through the organization's Github [0] and discovered a few nice packages. I'd happily pay for a good managed CD build system capable of handling projects / products with multiple dependencies. Right now I use CircleCI along with a bunch of scripts, and it works, but it's not great. One problem with ex…

Fwiw https://gocd.io/ handles pipelines (or graphs of multiple piplines) with several git repos just fine. That's on-premise, but not hard to run on your own. There's Snap CI, which is by ThoughtWorks (just as Go CD), and that's in the cloud. I don't know if they use the same code base, but it might be worth investigating if they can deal with multiple repos in a sensible way.

I wasn't responsible for setup, but we've been using Buildkite (https://buildkite.com) for our CI and it's been very nice. We run it through a Kubernetes cluster of workers and as far as I can tell it's been very flexible as to what's in a pipeline.

Re: Screwdriver: Yahoo's Continuous Delivery Build System for Dynamic Infrastructure

#54

Post by TeMPOraL »

userbinator wrote: post #40
ars wrote: post #3

For the confused: CD = Continuous Delivery, not Compact Disc. Mods: Perhaps edit the title?

I just hope Digital Versatile Delivery doesn't become a popular phrase in the future.

Introducing: Design Validation & Delivery.

You're welcome. ;).

Re: Screwdriver: Yahoo's Continuous Delivery Build System for Dynamic Infrastructure

#55

Post by hnbro »

ars wrote: post #3

For the confused: CD = Continuous Delivery, not Compact Disc. Mods: Perhaps edit the title?

why would someone think it was "compact disc"? even if a hn reader was somehow completely ignorant of continuous delivery, the context and usage should be a guide.

Re: Screwdriver: Yahoo's Continuous Delivery Build System for Dynamic Infrastructure

#56

Post by krakensden »

snnn wrote: post #48
krakensden wrote: post #15

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#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.

Chef cannot rollback. Chef is mainly for deployment but I think screwdriver focuses on CI. CD is not his business.

I mean, Chef Automate doesn't support rollback after all the usual toe dipping (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.

Re: Screwdriver: Yahoo's Continuous Delivery Build System for Dynamic Infrastructure

#57

Post by apercu »

camus2 wrote: post #34
andrewbinstock wrote: post #21

Earlier quoted context omitted.

They're still big in classical music. And, yes, classical music is still a thing too! ;-)

Jazz too, because of the older audience still buying physical goods.

Worship music as well (think churches).

Re: Screwdriver: Yahoo's Continuous Delivery Build System for Dynamic Infrastructure

#58

Post by rdsubhas »

perlgeek wrote: post #42
TheAceOfHearts wrote: post #37

Although Yahoo doesn't seem to be doing very well recently, they've done lots of great engineering. I recently looked through the organization's Github [0] and discovered a few nice packages. I'd happily pay for a good managed CD build system capable of handling projects / products with multiple dependencies. Right now I use CircleCI along with a bunch of scripts, and it works, but it's not great. One problem with ex…

Fwiw https://gocd.io/ handles pipelines (or graphs of multiple piplines) with several git repos just fine. That's on-premise, but not hard to run on your own. There's Snap CI, which is by ThoughtWorks (just as Go CD), and that's in the cloud. I don't know if they use the same code base, but it might be worth investigating if they can deal with multiple repos in a sensible way.

There are only 3 ways to model CI:

- Plain jobs (disconnected dots) (Jenkins/Travis-CI/etc)

- Full-on graphs with value stream maps and arbitrary connections (GoCD/Concourse/etc)

- Isolated pipelines (disconnected matrices/lists of columns) (Snap-CI/GitLab CI/etc)

I've lamented for a long time that there was no "lightweight" self-hosted pipeline tool that makes full use of modern tech (lightweight API, separate UI, offload the actual build environment to containers) and does nothing more than linking the pipeline and gets out of the way. Most organizations just don't have the engineering skills to handle build graphs. And the alternative job-style ends up in a complete mess.

Screwdriver fills a real void. I'm not a fanboy by any chance, but I'm really thankful to Yahoo for opening up this void so that many will follow.

Btw, Jenkins 2 Pipelines are not even in the picture because are neither proper pipelines nor proper jobs. It has no resumable/pausable stages, and is just a glorified DSL/UI on top of a multi-job kind of model.

Re: Screwdriver: Yahoo's Continuous Delivery Build System for Dynamic Infrastructure

#60

Post by edude03 »

specialist wrote: post #51
perlgeek wrote: post #42

Earlier quoted context omitted.

Fwiw https://gocd.io/ handles pipelines (or graphs of multiple piplines) with several git repos just fine. That's on-premise, but not hard to run on your own. There's Snap CI, which is by ThoughtWorks (just as Go CD), and that's in the cloud. I don't know if they use the same code base, but it might be worth investigating if they can deal with multiple repos in a sensible way.

We just switched to GoCD. And here I thought Jenkins sucked. I've never missed simple shell scripts, builds triggered by commits, tailing logs so much. Being closer to the metal. Back then, I had no idea the obvious solution was called "continuous integration". GoCD has a pretty dash board though. So I guess that's progress.

You should try concourse.ci then. I tried Circle gitlab go and concourse and concourse is the best so far.
Post reply on HN