https://github.com/eficode-academy/war-ci-servers
https://github.com/eficode-academy/war-ci-servers
Last synced: about 7 hours ago
JSON representation
- Host: GitHub
- URL: https://github.com/eficode-academy/war-ci-servers
- Owner: eficode-academy
- Created: 2020-02-04T09:19:29.000Z (about 5 years ago)
- Default Branch: master
- Last Pushed: 2024-08-11T05:28:28.000Z (9 months ago)
- Last Synced: 2025-04-07T08:37:51.568Z (26 days ago)
- Language: Java
- Size: 367 KB
- Stars: 6
- Watchers: 1
- Forks: 7
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# War of the CI servers
Repo used for the talk "War of the CI servers"
## Different CI's, same pipeline
We have tried to make the same pipeline in all the different CI systems, that should make them look like the image below:
Steps:
* **Clone down:** makes the git clone, and prepares the repo for being distributed to the parallel steps
* **Test:** runs the gradle test command found in [ci/unit-test-app.sh](ci/unit-test-app.sh)
* **Build:** runs the gradle build command found in [ci/build-app.sh](ci/build-app.sh)
* **Build docker:** runs [a linting of the dockerfile](ci/lint-dockerfile.sh), [building of the docker image](ci/build-docker.sh), and [pushes it up to the hub](ci/push-docker.sh)
* **System tests:** runs two tests, first [a k6 performance test with docker-compose](ci/performance-test.sh), thereafter a [docker-compose file](component-test/docker-compose.yml) with a [python test](component-test/test_app.py) to test the application.
Link to the pipelines:
* [Jenkinsfile pipeline](Jenkinsfile) written in declarative pipeline
* [GitlabCI](.gitlab-ci.yml)
* [CircleCI](.circleci/config.yml)
* [Github Actions](.github/workflows/gradle.yml)
* [Travis CI](.travis.yml)
## feedback and pull request
I would love to have more CI examples doing the same pipeline for comparison. PR are very welcome!