Solaris Stack

Product

Product development in this fast paced competitive tech world is not easy. Starting from internal process management to clean maintainable code. In order to building an hassle free scalable platform for your clients, you need to focus on delivering steady build on every iterations.

That’s why we created Solaris Stack

We take care of complete DevOps for you, while you focus on innovation and product development!

introducing Solaris stack

Jenkins provides us with various interfaces and tools in order to automate the entire process.

We have a Git repository where the development team will commit the code. Then, Jenkins takes over from there, a front-end tool where you can define your entire pipeline or the task.

Our job is to ensure the continuous integration and delivery process for that particular tool or for the particular application.

From Git, Jenkins pulls the code and then Jenkins moves it into the commit phase, where the code is committed from every branch. The build phase is where we compile the code. If it is Java code, we use tools like maven in Jenkins and then compile that code, which can be deployed to run a series of tests.

After the series of tests pass the Application is built as a Docker Image using the contents of the Docker file located from GitHub Repository.

The Docker image is then pushed to the Docker Hub based on the Authentication configuration described in Jenkins.

Jenkins pulls the built Docker Image from Docker Hub and Deploys it to the Kubernetes

Cluster as a part of the pipeline described in Jenkins File.

Kubernetes master server deploys the Docker image to the Kubernetes nodes based on the resources available in them.

The Application can now be accessed from the Kubernetes Node

Unified Dashboard

The entire pipeline is being Orchestrated by Jenkins, it can be viewed and monitored on a single dashboard where Prometheus acts as the Data Collector and Grafana is used as for Visualization of the various metrics.

Application Monitoring​

CPU, Memory and health of the Application running in Kubernetes Cluster can be monitored and visualized in Grafana

Infrastructure Monitoring

Prometheus and Grafana are also used to monitor the health of the Jenkins server and Infrastructure metrics of the Kubernetes Cluster.

Slack

The start time, end time and the total time taken for the builds are notified to the Users on Slack.

Jira

We integrate Jenkins with Jira and leverage Jira’s dashboard which displays the build status of Jenkins.

Close Menu