Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

adding ignite proposals #21

Merged
merged 1 commit into from about 2 years ago

2 participants

Marius Ducea Gildas Le Nadan
Marius Ducea
mdxp commented

No description provided.

Gildas Le Nadan endemics merged commit 86de43b into from
Gildas Le Nadan endemics closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Showing 1 unique commit by 1 author.

May 04, 2012
Marius Ducea mdxp adding ignite proposals febe420
This page is out of date. Refresh to see the latest.
25 site/content/events/2012-mountainview/proposals/ignite - Don't pay for a dumb broker/index.txt
... ... @@ -0,0 +1,25 @@
  1 +---
  2 +extension: html
  3 +filter:
  4 +- erb
  5 +- markdown
  6 +dirty: true
  7 +proposal: true
  8 +ignite: true
  9 +author: Patricio Arvizu
  10 +title: "Don't pay for a dumb broker."
  11 +---
  12 +**Abstract:**
  13 +
  14 +A lot of Continuous Integration tools today (both free and licensed) offer functionality out of the box or through plugins to do a variety of things. They all have pros and cons and are a great tool for startups and to quickly get on the Continous Delivery train.
  15 +
  16 +But consider the case of a company with multiple products. More than likely the build plans for both will be identical. So why would you need to have two separate projects? To further complicate matters, as your build/release needs change, you will have to maintain and update each plan separately. It becomes exponentially worse as the number of products increases.
  17 +
  18 +A better solution? Encapsulate the DSL for your build/release process in a single project, including all your build scripts. With this, two things can be achieved:
  19 +
  20 +1. The build system can be versioned and optionally released as an artifact. Either way, it becomes the first dependency for any product.
  21 +2. More importantly, your CI servers only need to be ""task brokers"" that invoke these scripts with no knowledge about the build process. Do you really want to pay for a "dumb" task broker?
  22 +
  23 +As a result of this, the build system artifact becomes the central repository of the build/release knowledge and saves you from update headaches in the future.
  24 +
  25 +**Proposer:** Patricio Arvizu, Build Automation Engineer for TheLadders.com
16 site/content/events/2012-mountainview/proposals/ignite - EverybodyOps/index.txt
... ... @@ -0,0 +1,16 @@
  1 +---
  2 +extension: html
  3 +filter:
  4 +- erb
  5 +- markdown
  6 +dirty: true
  7 +proposal: true
  8 +ignite: true
  9 +author: Stefan Zier
  10 +title: EverybodyOps
  11 +---
  12 +**Abstract:**
  13 +
  14 +Why and how all our developers carry the pager and deploy the system. We've practiced this here at Sumo Logic for the past year or so, with pretty good success, and I'd like to share some of the choices we made and what effect they've had. Somewhat similar to the NoOps practiced at Netflix, but at a much smaller scale.
  15 +
  16 +**Proposer:** Stefan Zier
20 site/content/events/2012-mountainview/proposals/ignite - Monitor All the Things/index.txt
... ... @@ -0,0 +1,20 @@
  1 +---
  2 +extension: html
  3 +filter:
  4 +- erb
  5 +- markdown
  6 +dirty: true
  7 +proposal: true
  8 +ignite: true
  9 +author: Jos Boumans
  10 +title: Monitor All the Things
  11 +---
  12 +**Abstract:**
  13 +
  14 +At Krux, we run at a pretty high traffic load from multiple sources (we provide infrastructure for big publishers), so we live and die by our monitoring and graphing.
  15 +
  16 +We use some clever tricks to measure everything we can get our hands on and are pushing about 300k metrics per seconds.
  17 +
  18 +I'd like to take 5 minutes and point folks at some of the tricks they could use to make their lives easier.
  19 +
  20 +**Proposer:** Jos Boumans

Tip: You can add notes to lines in a file. Hover to the left of a line to make a note

Something went wrong with that request. Please try again.