Skip to content

Commit 289d676

Browse files
mattmakaimattmakai
committed
working on CI page
1 parent 9add9ec commit 289d676

File tree

7 files changed

+29
-15
lines changed

7 files changed

+29
-15
lines changed

‎all.html‎

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2431,16 +2431,20 @@ <h2>Why is continuous integration important?</h2>
24312431
do not break existing tests ensure the software works as intended.</p>
24322432
<h2>Continuous integration example</h2>
24332433
<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
2434+
integration and deployment can work. </p>
2435+
<p><img src="theme/img/continuous-integration.png" width="100%" class="technical-diagram" alt="One potential way for continuous integration to work." /></p>
2436+
<p>In the above diagram, when new code is commited to a source repository
2437+
there is a hook that notifies the continuous integration server that new
2438+
code needs to be built (the continuous integration server could also
24372439
poll the source code repository if a notification is not possible).</p>
24382440
<p>The continuous integration server pulls the code to build and test it. If
24392441
all tests pass, the continuous integration server begins the deployment
24402442
process. The new code is pulled down to the server where the deployment is
24412443
taking place. Finally the deployment process is completed via restarting
24422444
services and related deployment activities.</p>
2443-
<p><img src="theme/img/continuous-integration.png" width="100%" class="technical-diagram" alt="One potential way for continuous integration to work." /></p>
2445+
<p>There are many other ways a continuous integration server and its
2446+
deployments can be structured. The above was just one example of a
2447+
relatively simple set up.</p>
24442448
<h2>Open source CI projects</h2>
24452449
<ul>
24462450
<li>

‎continuous-integration.html‎

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -49,16 +49,20 @@ <h2>Why is continuous integration important?</h2>
4949
do not break existing tests ensure the software works as intended.</p>
5050
<h2>Continuous integration example</h2>
5151
<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
52+
integration and deployment can work. </p>
53+
<p><img src="theme/img/continuous-integration.png" width="100%" class="technical-diagram" alt="One potential way for continuous integration to work." /></p>
54+
<p>In the above diagram, when new code is commited to a source repository
55+
there is a hook that notifies the continuous integration server that new
56+
code needs to be built (the continuous integration server could also
5557
poll the source code repository if a notification is not possible).</p>
5658
<p>The continuous integration server pulls the code to build and test it. If
5759
all tests pass, the continuous integration server begins the deployment
5860
process. The new code is pulled down to the server where the deployment is
5961
taking place. Finally the deployment process is completed via restarting
6062
services and related deployment activities.</p>
61-
<p><img src="theme/img/continuous-integration.png" width="100%" class="technical-diagram" alt="One potential way for continuous integration to work." /></p>
63+
<p>There are many other ways a continuous integration server and its
64+
deployments can be structured. The above was just one example of a
65+
relatively simple set up.</p>
6266
<h2>Open source CI projects</h2>
6367
<ul>
6468
<li>

‎feeds/all.atom.xml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,2 @@
11
<?xml version="1.0" encoding="utf-8"?>
2-
<feed xmlns="http://www.w3.org/2005/Atom"><title>Matt Makai</title><link href="http://www.fullstackpython.com/" rel="alternate"></link><link href="http://www.fullstackpython.com/feeds/all.atom.xml" rel="self"></link><id>http://www.fullstackpython.com/</id><updated>2014-11-21T17:06:51Z</updated></feed>
2+
<feed xmlns="http://www.w3.org/2005/Atom"><title>Matt Makai</title><link href="http://www.fullstackpython.com/" rel="alternate"></link><link href="http://www.fullstackpython.com/feeds/all.atom.xml" rel="self"></link><id>http://www.fullstackpython.com/</id><updated>2014-11-21T17:09:05Z</updated></feed>

‎source/content/pages/06-automation/0602-continuous-integration.markdown‎

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -28,9 +28,13 @@ do not break existing tests ensure the software works as intended.
2828

2929
## Continuous integration example
3030
The following picture represents a high level perspective on how continuous
31-
integration and deployment can work. When new code is commited to a source
32-
repository there is a hook that notifies the continuous integration server
33-
that new code needs to be built (the continuous integration server could also
31+
integration and deployment can work.
32+
33+
<img src="theme/img/continuous-integration.png" width="100%" class="technical-diagram" alt="One potential way for continuous integration to work." />
34+
35+
In the above diagram, when new code is commited to a source repository
36+
there is a hook that notifies the continuous integration server that new
37+
code needs to be built (the continuous integration server could also
3438
poll the source code repository if a notification is not possible).
3539

3640
The continuous integration server pulls the code to build and test it. If
@@ -39,7 +43,9 @@ process. The new code is pulled down to the server where the deployment is
3943
taking place. Finally the deployment process is completed via restarting
4044
services and related deployment activities.
4145

42-
<img src="theme/img/continuous-integration.png" width="100%" class="technical-diagram" alt="One potential way for continuous integration to work." />
46+
There are many other ways a continuous integration server and its
47+
deployments can be structured. The above was just one example of a
48+
relatively simple set up.
4349

4450

4551
## Open source CI projects

‎source/mockups/continuous-integration.bmml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<mockup version="1.0" skin="sketch" fontFace="Balsamiq Sans" measuredW="999" measuredH="539" mockupW="873" mockupH="513">
1+
<mockup version="1.0" skin="sketch" fontFace="Balsamiq Sans" measuredW="884" measuredH="488" mockupW="698" mockupH="434">
22
<controls>
33
<control controlID="4" controlTypeID="__group__" x="222" y="290" w="240" h="128" measuredW="240" measuredH="128" zOrder="1" locked="false" isInGroup="-1">
44
<groupChildrenDescriptors>
@@ -15,7 +15,7 @@
1515
</control>
1616
</groupChildrenDescriptors>
1717
</control>
18-
<control controlID="5" controlTypeID="com.balsamiq.mockups::Canvas" x="126" y="26" w="873" h="513" measuredW="100" measuredH="70" zOrder="0" locked="false" isInGroup="-1">
18+
<control controlID="5" controlTypeID="com.balsamiq.mockups::Canvas" x="186" y="54" w="698" h="434" measuredW="100" measuredH="70" zOrder="0" locked="false" isInGroup="-1">
1919
<controlProperties>
2020
<borderColor>16777215</borderColor>
2121
</controlProperties>

‎source/theme/static/img/continuous-integration.png‎

-1.41 KB
Loading

‎theme/img/continuous-integration.png‎

-1.41 KB
Loading

0 commit comments

Comments
 (0)