aboutsummaryrefslogtreecommitdiffstats
path: root/docs/integration-CICD.rst
diff options
context:
space:
mode:
authorLasse Kaihlavirta <l.kaihlavirt@partner.samsung.com>2020-11-18 16:54:36 +0200
committerLasse Kaihlavirta <l.kaihlavirt@partner.samsung.com>2020-11-18 16:54:36 +0200
commit2d2888ad342bad966397c0c258449f4e74c3f0ce (patch)
tree950d2df3019d910466f70d769bd88366c1f0cbc2 /docs/integration-CICD.rst
parent5676b62ebb839b9dec32c4ebed6c34dbb31ce825 (diff)
Correct typos and grammar
Issue-ID: INT-1736 Signed-off-by: Lasse Kaihlavirta <l.kaihlavirt@partner.samsung.com> Change-Id: Ife9a7f973686474d2a8e7ad91318244299fb178c
Diffstat (limited to 'docs/integration-CICD.rst')
-rw-r--r--docs/integration-CICD.rst20
1 files changed, 10 insertions, 10 deletions
diff --git a/docs/integration-CICD.rst b/docs/integration-CICD.rst
index 298b292f4..f7d9f0790 100644
--- a/docs/integration-CICD.rst
+++ b/docs/integration-CICD.rst
@@ -19,7 +19,7 @@ Continuous Integration
The CI part provides the following features:
- Repository Verification (format of the INFO.yaml)
-- Patchset verification thank to json/yaml/python/go/rst/md linters. These jenkins
+- Patchset verification thank to json/yaml/python/go/rst/md linters. These Jenkins
verification jobs are hosted in the ci-management repository. They can vote
+1/-1 on patchset submission. Integration team systematically enables linters
on any new repository
@@ -45,24 +45,24 @@ There are 2 Continuous Deployment architectures.
Jenkins CD on Windriver/Intel lab
..................................
-The CD part on windriver/Intel is based on jenkins.
+The CD part on Windriver/Intel is based on Jenkins.
-It is based on a standalone VM hosting a jenkins server.
-The credentials of this VM as well as the jenkins server have been provided to
+It is based on a standalone VM hosting a Jenkins server.
+The credentials of this VM as well as the Jenkins server have been provided to
integration committers.
-Several jobs can be triggered from this jenkins interface.
+Several jobs can be triggered from this Jenkins interface.
Historically several chains were run daily (staging/release) but due to
performance issues, they have all been stopped.
Only SB-00 has been kept for use case support.
-The jenkins interface was however used to launch the installation of SB-00.
+The Jenkins interface was however used to launch the installation of SB-00.
-This jenkins script is leveraging resources available in OOM and integration
+This Jenkins script is leveraging resources available in OOM and integration
repositories.
-It was planned to replaced this CD by a gitlab runner based CD to unify the CD
-management. But due to performance issue in the DC it was not possible to
-finalize the operation in Guilin.
+The replacement of this CD by a gitlab runner based CD to unify the CD
+management was planned, but finalizing the operation in Guilin was not possible
+due to performance issues.
Gitlab CD
.........