Removed link to 404 page

Container Based Builds: removed a link to a missing docker article.

radar/2017-03-01/container-based-builds.md

@@ -9,4 +9,4 @@ Running your builds in isolated containers keeps your build servers clean. It al
 
 Note that you need to think about some kind of caching mechanism for your depenendies to avoid downloading them in every build, which would cause long build times.
 
-At AOE, we are currently starting to use this approach for building services and it is especially useful if your build has special dependencies. Also, it's possible to use GitLab as a build tool or use [Docker with the new Jenkinspipeline](https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Docker+Pipeline+Plugin). For caching we are evaluating minio as a cache server. We noticed that our builds run quite rapidly and reliably with that. Also, the complexity of the builds decreased since we don't need any workarounds, which were caused by having everything installed on one build server.
+At AOE, we are currently starting to use this approach for building services and it is especially useful if your build has special dependencies. Also, it's possible to use GitLab as a build tool or use Docker with the new Jenkinspipeline. For caching we are evaluating minio as a cache server. We noticed that our builds run quite rapidly and reliably with that. Also, the complexity of the builds decreased since we don't need any workarounds, which were caused by having everything installed on one build server.