Cyclist cycling around large bend

CogBoard: informing agile delivery

24 January 2020Wiktoria Noga

It’s now widely acknowledged that continuous integration and continuous delivery are beneficial practices for a modern business.

Continuous delivery was introduced by Jez Humble and David Farley to extend the practice of continuous integration. Both reduce the risk associated with waterfall development cycles, where months of complex development were vested in one moment of truth – the Go Live. 


Continuous development cycles see developers pushing new code to a central depository as frequently as possible where they are then subjected to a series of automated tests. Continuous integration focuses on avoiding enormous code conflicts at the end of a build cycle by merging code created by multiple developers several times a day. Continuous delivery ensures that the code can be released at any time, keeping it in a constantly deployable state so that a new feature can be turned on instantly. Combined, they allow businesses to manage their processes with greater efficiency and reliability, enabling them to provide new software products and features more quickly and more often.


Aggregating the data

So, continuous integration and continuous delivery are good for business. But we challenged ourselves to make it better. Bringing huge amounts of new code together and readying it for deployment relies on enormous amounts of data from various sources. As ever, with data, the challenge is not just to have it, but to make it accessible, easy to analyse and actionable. So, we set ourselves the task of aggregating the data around continuous delivery and presenting it to the entire team in a single, intuitive interface.

Having researched developers needs, we iterated and had some fun with names for our new tool, such as Smashing and Dashing. The product evolved and is now a tool that we are super proud of. So, we’re releasing CogBoard to the open source community.


CogBoard Logo

What is CogBoard?

CogBoard gathers data from a wide range of external sources – AEM, Bamboo, Jenkins, SonarQube etc. - and displays the information on personalised dashboards. It provides teams with continuous information on the delivery status of any project and arms them with the ability to continuously react to any issues. Think of it as an always-on, data-driven issue alert system.

CogBoard Dashboard example

How does it work?

CogBoard is based on the latest technologies, Kotlin Language, Docker Containers, Reactive Frameworks and Cypress, to name a few. It works with continuous delivery tools like Jenkins and Bamboo SonarQube and, most importantly, it works with Adobe Experience Manager.


Developers can create their own personalised dashboards, using the widgets that we’ve created or, now that it’s open source, by creating new ones and contributing to the project.


How will it benefit my project?

Better project status visibility.With data gathered in one place, your teams will have visibility across all the environments they are responsible for.


Time saving. Dismissing the need for teams to trawl their mailboxes for information, or to log into separate data sources, CogBoard saves huge amounts of time.


Greater agility.With data spread across separate sources, teams may typically pull together a delivery status report once a week. CogBoard provides up-to-the-minute information, all the time, so that you can constantly and immediately react to issues that may arise.


Improved collaboration. With CogBoard, everyone on the team gets access to the same information. This inevitably improves teamwork and means that anyone can be a ‘life saver’ when needed.


Join our community and get access to CogBoard

Anyone and everyone can now get access to CogBoard and its benefits. It’s easy to set up and you can contribute to the project via GitHub. Please read our Collaboration Information and Code of Conduct in order to learn more. Alternatively email us to join the CogBoard conversation .


CogBoard is licensed under Apache License, Version 2.0.

Author: Wiktoria Noga
Published: 24 January 2020
Tags:
AEMopen sourcecontinous deliveryQAagile
 

People in or team love to share their experience. Explore our blog

Job Opportunities

We're always looking for new faces to join the Cognifide family. Take a look at our available jobs.