You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: all.html
+13Lines changed: 13 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -2429,6 +2429,18 @@ <h2>Why is continuous integration important?</h2>
2429
2429
checked by automated tests. Source code changes as a project evolves.
2430
2430
CI combined with unit and integration tests check that code modifications
2431
2431
do not break existing tests ensure the software works as intended.</p>
2432
+
<h2>Continuous integration example</h2>
2433
+
<p>The following picture represents a high level perspective on how continuous
2434
+
integration and deployment can work. When new code is commited to a source
2435
+
repository there is a hook that notifies the continuous integration server
2436
+
that new code needs to be built (the continuous integration server could also
2437
+
poll the source code repository if a notification is not possible).</p>
2438
+
<p>The continuous integration server pulls the code to build and test it. If
2439
+
all tests pass, the continuous integration server begins the deployment
2440
+
process. The new code is pulled down to the server where the deployment is
2441
+
taking place. Finally the deployment process is completed via restarting
2442
+
services and related deployment activities.</p>
2443
+
<p><imgsrc="theme/img/continuous-integration.png" width="100%" class="technical-diagram" alt="One potential way for continuous integration to work." /></p>
2432
2444
<h2>Open source CI projects</h2>
2433
2445
<ul>
2434
2446
<li>
@@ -4117,6 +4129,7 @@ <h1>Change Log</h1>
4117
4129
<h2>2014</h2>
4118
4130
<h3>November</h3>
4119
4131
<ul>
4132
+
<li>Adding a nice new continuous integration diagram.</li>
4120
4133
<li>More Django and database resources.</li>
4121
4134
<li>Revising development environments page and adding new resources.</li>
4122
4135
<li>Adding my new Flask blog post on choose your own adventure presentations
Copy file name to clipboardExpand all lines: continuous-integration.html
+12Lines changed: 12 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -47,6 +47,18 @@ <h2>Why is continuous integration important?</h2>
47
47
checked by automated tests. Source code changes as a project evolves.
48
48
CI combined with unit and integration tests check that code modifications
49
49
do not break existing tests ensure the software works as intended.</p>
50
+
<h2>Continuous integration example</h2>
51
+
<p>The following picture represents a high level perspective on how continuous
52
+
integration and deployment can work. When new code is commited to a source
53
+
repository there is a hook that notifies the continuous integration server
54
+
that new code needs to be built (the continuous integration server could also
55
+
poll the source code repository if a notification is not possible).</p>
56
+
<p>The continuous integration server pulls the code to build and test it. If
57
+
all tests pass, the continuous integration server begins the deployment
58
+
process. The new code is pulled down to the server where the deployment is
59
+
taking place. Finally the deployment process is completed via restarting
60
+
services and related deployment activities.</p>
61
+
<p><imgsrc="theme/img/continuous-integration.png" width="100%" class="technical-diagram" alt="One potential way for continuous integration to work." /></p>
0 commit comments