Skip to content

Commit 26cd51b

Browse files
committed
updated
1 parent fa268b0 commit 26cd51b

33 files changed

Lines changed: 230 additions & 0 deletions

slides/docker/bower.json

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
{
2+
"name": "docker-jenkins",
3+
"version": "0.0.0",
4+
"dependencies": {
5+
"reveal.js": "~2.6.1",
6+
"reveal-highlight-themes": "~8.3.0"
7+
}
8+
}

slides/docker/slides/about.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
<!-- .slide: data-background="#795548" -->
2+
# What is all about?
3+
4+
* Development vs Testing Environment
5+
* Using Docker for Testing
6+
* Overview of CI Servers
7+
* Running Paralell Jobs
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
<!-- .slide: data-background="/img/architecture.svg" data-background-size="600px" data-background-color="#DCEDC8" -->
Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
<!-- .slide: data-background="#455A64" -->
2+
3+
# Build Matrix
4+
5+
1. Configure axis
6+
2. Combinate values
7+
3. Use current values as environment vars

slides/docker/slides/ci.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
<!-- .slide: data-background="#c0392b" -->
2+
3+
### Continuous Integration (CI) is a development practice that requires developers to integrate code into a shared repository several times a day. Each check-in is then verified by an automated build, allowing teams to detect problems early.
4+
5+
*[thoughtworks.com/continuous-integration](http://www.thoughtworks.com/continuous-integration)*

slides/docker/slides/conclusion.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
<!-- .slide: data-background="#2c3e50" -->
2+
3+
# Conclusions
4+
5+
* Test execution time can be improved by running tests in parallel
6+
* Docker makes easy to run isolated concurrent builds

slides/docker/slides/concurrent.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
<!-- .slide: data-background="#38264c" -->
2+
3+
# Running Parallel Builds
4+
5+
* **TravisCI**: out-of-box. Runs same tests suites for different language versions. I.e. PHP 5.3, 5.4, 5.5
6+
* **JenkinsCI**: using multi-configuration project (MatrixReloaded plugin). Builds can be executed on slave servers.

slides/docker/slides/container.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
<!-- .slide: data-background="/img/docker_container.png" data-background-size="800px" data-background-color="#7A8F94" -->

slides/docker/slides/docker.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
<!-- .slide: data-background="/img/docker-logo.png" data-background-size="900px" -->
2+
3+
##### Or Use
Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
# Docker Container
2+
3+
* Running container != booting OS
4+
* No daemons will be executed on start
5+
* Only one process can be run at once

0 commit comments

Comments
 (0)