The Netflix Tech Blog: How We Build Code at Netflix

I haven’t made the time to read this properly yet; so far half the terms mean nothing at all to me. It’ll be interesting to find out.

The above diagram expands on a previous post announcing Spinnaker, our global continuous delivery platform. There are a number of steps that need to happen before a line of code makes it way into Spinnaker:
Code is built and tested locally using Nebula
Changes are committed to a central git repository
A Jenkins job executes Nebula, which builds, tests, and packages the application for deployment
Builds are “baked” into Amazon Machine Images
Spinnaker pipelines are used to deploy and promote the code change

via The Netflix Tech Blog: How We Build Code at Netflix


The Process Myth

Ah, this one is worth reading beginning to end: The Process Myth.

Engineers don’t hate process. They hate process that can’t defend itself.

Capybara/Poltergeist/PhantomJS blacklisting

Poltergeist supports URL blacklisting which allows you to prevent scripts from running on designated domains. If you are experiencing slower run times, consider creating a URL blacklist of domains that are not essential to your testing environment, such as ad networks or analytics.

page.driver.browser.url_blacklist = ['']

Make sure you set it before each running test, because this setting’s cleaned up when capybara does reset.

for example like so:

config.before(:each, js: true) do
    page.driver.browser.url_blacklist = [""]

via teampoltergeist/poltergeist: A PhantomJS driver for Capybara.