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: content/pages/05-deployment/27-continuous-integration.markdown
+15-1Lines changed: 15 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,7 +45,7 @@ intended.
45
45
The following picture represents a high level perspective on how continuous
46
46
integration and deployment can work.
47
47
48
-
<imgsrc="/img/visuals/continuous-integration.png"width="100%"class="technical-diagram"alt="One potential way for continuous integration to work with source control and a deployment environment." />
48
+
<imgsrc="/img/visuals/continuous-integration.png"width="100%"class="shot"alt="One potential way for continuous integration to work with source control and a deployment environment." />
49
49
50
50
In the above diagram, when new code is committed to a source repository
51
51
there is a hook that notifies the continuous integration server that new
@@ -157,3 +157,17 @@ programming language agnostic. Learn more via the following resources or on
157
157
strongly advises securing your continuous integration server just as you
158
158
would every other part of your production application, unless you want
159
159
your environment to be vulnerable to malicious actors.
160
+
161
+
*[Measuring and Improving your CI/CD Pipelines](https://blog.petegoo.com/2018/11/09/optimizing-ci-cd-pipelines/)
162
+
provides metrics for what you should measure with your CI/CD setup to
163
+
improve the process for helping your development teams ship code.
164
+
165
+
*[Six rules for setting up continuous integration systems](https://rhonabwy.com/2016/01/31/six-rules-for-setting-up-continuous-integration-systems/)
166
+
has some solid general advice for culling problematic tests, ensuring
167
+
the integration speed supports the development culture you are building
168
+
and keeping all code in source control instead of having complicated
169
+
logic configured within the CI server.
170
+
171
+
*[How to Identify Major Blockers in a CI/CD Pipeline](https://blog.codeship.com/how-to-identify-major-blockers-in-a-cicd-pipeline/)
172
+
gives a high level overview of concepts such as shipping velocity, test
173
+
execution and environment provisioning with regards to CI configurations.
0 commit comments