How to easily Build a CI dashboard


The code that is never executed for users is like a digital waste product. To prevent the building of waste and to showcase the results of code on the Kubernetes environment, we can use CI Dashboard, with chaos testing.

CI-E2E Flow Diagram
CI-E2E Flow Diagram

The CI dashboard allows the users to view the commit and release based build along with chaos test using litmus on a different platform with different kubernetes versions.

In this tutorial, we’ll go through all the steps for setting up the Ci dashboard

  1. Create a project
  2. Push the code to GitHub
  3. Setup the CI of the project using gitlab
  4. Select the chaos test from litmus.
  5. Add the script in gitlab yaml to create pipelines for executing the chaos tests
  6. Build a CI dashboard(ex: ) to display the gitlab pipeline history and status
  7. Conclusion

Step 1: Create a project

Create a project and write some automated test for it, Also add the Dockerfile in the project to set up the CI.

Step 2: Put the codes on GitHub

Create a repository on GitHub and add .gitignore file for ignoring the auto-generated folder or file, Follow the below script to put changes to GitHub.

$ git init
$ git add .
$ git commit -s -m "Initial commit"
$ git remote add origin <origin_url>.git
$ git push origin master

Step 3: Setup the CI using gitlab

Add .gitlab.yaml file to project and write the build and test steps in it. (Ex: Import the project in gitlab from GitHub. Setup the gitlab pipeline environment variable to push the docker image or any other if required. Add the pipeline trigger command in .gitlab.yaml file.

Step 4: Selection of chaos test

Select the chaos test(litmus book) from litmus repository or write your own litmus book if needed which will test the product performance on different kubernetes version as well as different cloud vendors.

Step 5: Add script in gitlab.yaml

Create a repository for the execution of the platform-based pipeline. Add .gitlab.yaml file and related script to create a cluster or using the executing cluster and run the different chaos test in different stages of the pipeline.

Reference of .gitlab.yaml file

when: always
image: chandankumar4/packet:v4
- packet-cluster
- chmod 755 ./script/packet-cleanup
- ./script/packet-cleanup

Step 6: Build a CI dashboard

CI Dashboard
CI Dashboard

Create a project called Ci dashboard backend which will fetch the pipeline details form gitlab, By accessing their API and expose the same on different API after some enhancement. Create another project called Ci dashboardwhich will display the gitlab pipeline details by accessing the data from backend API.

Step 7: Conclusion

CI dashboard will display the build history of the imported project and their performance on a different platform with different Kubernetes version.


openebs/ci-e2e-dashboardContribute to openebs/ci-e2e-dashboard development by creating an account on

openebs/ci-e2e-dashboard-go-backendOpenEBS CI Dashboard backend using Go and PostgreSQL. — openebs/

openebs/mayaOpenEBS Maya extends Kubernetes capabilities to orchestrate CAS containers. — openebs/


This article was first published on Apr 26, 2019 on OpenEBS's Medium Account

Murat Karslioglu
VP @OpenEBS & @MayaData_Inc. Murat Karslioglu is a serial entrepreneur, technologist, and startup advisor with over 15 years of experience in storage, distributed systems, and enterprise hardware development. Prior to joining MayaData, Murat worked at Hewlett Packard Enterprise / 3PAR Storage in various advanced development projects including storage file stack performance optimization and the storage management stack for HPE’s Hyper-converged solution. Before joining HPE, Murat led virtualization and OpenStack integration projects within the Nexenta CTO Office. Murat holds a Bachelor’s Degree in Industrial Engineering from the Sakarya University, Turkey, as well as a number of IT certifications. When he is not in his lab, he loves to travel, advise startups, and spend time with his family. Lives to innovate! Opinions my own!
Utkarsh Mani Tripathi
Jeffry Molanus
Jeffry prior to being CTO at MayaData has worked at several other startups in the storage industry. He worked on several scale out object storage products as well as traditional NAS and SAN storage solutions where he held technical leadership roles. At MayaData, his primary focus will be around making sure the product is flexible and scalable yet robust enough to be integrated seamlessly into modern day infrastructure where he believes, containers will have a dominant role. Jeffry holds a master degree in electrical engineering with a focus on distributed control engineering from the University Twente in the Netherlands. When he is not working with code, he practices martial arts.