From e6e221263a7ce6d5625e182a909696bc4d58ec25 Mon Sep 17 00:00:00 2001
From: Paulo Pires <pjpires@gmail.com>
Date: Fri, 17 Apr 2015 20:11:12 +0100
Subject: [PATCH] Removed duplicated markdown file with a different name.

---
 .../docs/rollingupdates_from_jenkins.md       | 57 -------------------
 1 file changed, 57 deletions(-)
 delete mode 100644 contrib/recipes/docs/rollingupdates_from_jenkins.md

diff --git a/contrib/recipes/docs/rollingupdates_from_jenkins.md b/contrib/recipes/docs/rollingupdates_from_jenkins.md
deleted file mode 100644
index 310aebb6682..00000000000
--- a/contrib/recipes/docs/rollingupdates_from_jenkins.md
+++ /dev/null
@@ -1,57 +0,0 @@
-###How To
-For our example, Jenkins is set up to have one build step in bash:
-
-`Jenkins "Bash" build step`
-```
-    #!/bin/bash
-    cd $WORKSPACE
-    source bin/jenkins.sh
-    source bin/kube-rolling.sh
-```
-
-Our project's build script (`bin/jenkins.sh`), is followed by our new kube-rolling script. Jenkins already has `$BUILD_NUMBER` set, but we need a few other variables that are set in `jenkins.sh` that we reference in `kube-rolling.sh`:
-
-```
-    DOCKER_IMAGE="path_webteam/public"
-	REGISTRY_LOCATION="dockerreg.web.local/"
-```
-
-Jenkins builds our container, tags it with the build number, and runs a couple rudimentary tests on it. On success, it pushes it to our private docker registry. Once the container is pushed, it then executes our rolling update script.
-
-`kube-rolling.sh`
-```
-    #!/bin/bash
-    # KUBERNETES_MASTER: Your Kubernetes API Server endpoint
-    # BINARY_LOCATION:   Location of pre-compiled Binaries (We build our own, there are others available)
-    # CONTROLLER_NAME:   Name of the replicationController you're looking to update
-    # RESET_INTERVAL:    Interval between pod updates
-
-    export KUBERNETES_MASTER="http://10.1.10.1:8080"
-    BINARY_LOCATION="https://build.web.local/kubernetes/"
-    CONTROLLER_NAME="public-frontend-controller"
-    RESET_INTERVAL="10s"
-
-    echo "*** Time to push to Kubernetes!";
-
-    #Delete then graba kubecfg binary from a static location
-    rm kubecfg
-    wget $BINARY_LOCATION/kubecfg
-
-    echo "*** Downloaded binary from $BINARY_LOCATION/kubecfg"
-
-    chmod +x kubecfg
-
-    # Update the controller with your new image!
-    echo "*** ./kubecfg -image \"$REGISTRY_LOCATION$DOCKER_IMAGE:$BUILD_NUMBER\" -u $RESET_INTERVAL rolling-update $CONTROLLER_NAME"
-    ./kubecfg -image "$REGISTRY_LOCATION$DOCKER_IMAGE:$BUILD_NUMBER" -u $RESET_INTERVAL rolling-update $CONTROLLER_NAME
-```
-
-Though basic, this implementation allows our Jenkins instance to push container updates to our Kubernetes cluster without much trouble.
-
-### Notes
-When using a private docker registry as we are, the Jenkins slaves as well as the Kubernetes minions require the [.dockercfg](https://coreos.com/docs/launching-containers/building/customizing-docker/#using-a-dockercfg-file-for-authentication) file in order to function properly.
-
-### Questions
-twitter @jeefy
-
-irc.freenode.net #kubernetes jeefy