Hello my dear readers. Welcome back to my next sprint retrospective blog post for all of you who have been following me through my journey and welcome to all new readers (I would strongly suggest you to read all the sprint so you are familiar what I am talking about). Are you excited to know what we have been up to this past sprint?!

The other team working on this project was able to push their changed and the professor merged and deployed their changes. I got to say they did a very good job in the tool bar. Now it is our time to add our search bar. While doing that we were thinking that we wanted to work on some other stuff in the project to feel more productive. We started to look at the issues that were listed in the github repository but an idea crossed my mind.

I am taking this class in parallel with another software development concentration class: CS 348, Software Process Management. There were two classes were our professor wanted to teach us about CI/CD and Travis CI. Yeah I know most of you are like: “English please!” For all of you that are not familiar with the terms, CI means continues integration, CD means continues deployment and Travis CI is a software used to set up your project with CI/CD. But why is good to CI/CD?

First time I cam across with CI/CD  it was at work, when one of my teammates suggested to have CI/CD in one of our systems. After his idea was approved, he set up our system with CI/CD and it was seriously a life savior! At my work place we use two main branches: dev and master. Dev branch is for all developers to merge and test their changes in a live environment. Dev is not production. Master branch is the production branch where only managers can merge and deploy. Whenever a change is made, we merge our branch into the dev branch and that’s where CI/CD kicks in and makes everything easy. Before we had to wait for the managers to deploy our changes to dev and then we could test. Long story short, CI/CD made us more productive and efficient.

My idea was to set up the AMPATH project with the CI/CD via Travis CI. The good thing about using Travis is that differently from Jenkins you don’t need a server. We talked with our professor and we were very happy that the idea was welcomed and approved. While me and Kristi will be working on integration for the next sprint, the other team members will be picking up another issue.

This past sprint was mostly a reflection on what we have worked on and what else we should do. I am very excited for the next sprint though, as this is the last sprint and then we have to present our work. I am really looking forward to figuring out how to set up an angular project with Travis CI and make everyone’s job easier. Please don’t miss my last sprint for this capstone class..See ya next time 🙂