Skip to content

armgit / core

Public Imported from GitHub
0

100% open-source IoT Platform - Integrate your devices, add intelligence, build custom apps

Gitlab docs WIP

Michal Rutka74f846de1edf
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 816e17287..1bce9f62f 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -23,6 +23,7 @@ lint-Dockerfile:
rules:
- if: $CI_COMMIT_BRANCH == "master"
if: $CI_COMMIT_MESSAGE !~ /skip-build/
+ when: manual
lint-swarm-Dockerfile:
stage: build
@@ -121,7 +122,6 @@ test-master:
artifacts:
when: on_failure
paths:
- - /or/test/build/reports/tests/test/index.html
- "test/build/reports/tests/test/*"
- "test/build/reports/tests/test/*/*"
expire_in: 2 weeks
diff --git a/gitlab-ci/README.md b/gitlab-ci/README.md
index 537ab1382..cf1221b5f 100644
--- a/gitlab-ci/README.md
+++ b/gitlab-ci/README.md
@@ -5,20 +5,27 @@ If one imports main repo the pipeline can be started.
## Build docker images
-You can skip this stage by adding skip-build in the git commit message.
+You can skip this stage by adding **skip-build** in the git commit message.
## Test the stack
-You can skip this stage by adding skip-test in the git commit message.
+The second major step in the CI/CD pipeline are functional tests. When extending
+the functionality, e.g. by adding a new protocol, tests covering its behaviour should
+be included to the main branch and executed during each commit and check whether no
+legacy functionality is broken. Sometimes this is intended and in this case rgresssion
+tests should be adjusted to the new situation.
+
+In case that no functionaity is changed, e.g. in case of documentation updates, this stage can
+be skipped by adding **skip-test** in the git commit message.
### Inspect failed test report output
-After running a failed pipleine the test report is stored as artifacts. On the right side of the failed pipleine there is a link
-where reports can be downloaded.
+When tests fail and break the pipeline, test reports are stored as artifacts. On the right side of the failed pipleine there is a link
+where the reports can be downloaded.
## Deploy
-You can skip this stage by adding skip-deploy in the git commit message.
+You can skip this stage by adding **skip-deploy** in the git commit message.
# Deploing OpenRemote stack in the cloud