Construction, Build Flow, and CI/CD

First and foremost, and while it mightn’t be immediately obvious, Build Flow is a software company...

We just happen to assist Melbourne and Victorian-based home owners and builders, contractors, labourers, project managers, and more, with a core focus and drive to assist people in the construction industry...

We figured that, with our eye on innovation and involvement in this industry, that we could not only attempt to offer a suite of services in demolitions, renovations, and asbestos removal, but actually help those already doing these jobs - utilising the awesome power of automation. We’ve covered off our individual service offerings and described our business in a lot of detail in other blog posts and on our website, but now we’d like to talk more about what makes us unique among all the other construction businesses, project management companies, and demolition experts.

One of the reasons our company is so innovative, is not just applying automation to this particular vertical, but rather through a concept called CI/CD - continuous integration and continuous development/delivery.  Our friends at Atlassian, with one of their products actually a core driver of our automation system, define these terms below:

Continuous integration: CI is where, after making changes to workflows or your automation system, your changes are merged “back to the main branch as often as possible,” and “validated by creating a build and running automated tests against the build.  

Continuous delivery: “is an extension of continuous integration since it automatically deploys all code changes to a testing and/or production environment after the build stage. 

This means that on top of automated testing, you have an automated release process and you can deploy your application any time by clicking a button.”

Continuous deployment: “goes one step further than continuous delivery. With this practice, every change that passes all stages of your production pipeline is released to your customers. There's no human intervention, and only a failed test will prevent a new change to be deployed to production.

Continuous deployment is an excellent way to accelerate the feedback loop with your customers and take pressure off the team as there isn't a Release Day anymore. Developers can focus on building software, and they see their work go live minutes after they've finished working on it.”

While these things may seem like very developer-heavily terms, they’re surprisingly applicable to us and what we do here at Build Flow, where we can pass the advances that CI/CD give onto you, as a home buyer/builder, contractor, labourer, or project manager. To summarise these concepts in plain english, continuous integration sees changes to a workflow made and then immediately, but manually implemented to the wider system, continuous delivery deploys the changes without the need for manual implementation, and continuous deployment goes even further, by automatically integrating changes every time they are made, straight to the consumer or user of your workflow/system.  

What does this all mean?

It basically means that the workflows that enable us to deliver faster, cheaper, and safer demolitions, construction jobs, or asbestos removals, are constantly improving, with each iteration that is provided to us by you, the user. We, along with out system, are constantly taking note of how things can be better - maybe we need to rearrange the steps in our process, use another service provider, figure out a different way to send you a quote, use another way of contacting the council - and then integrating all optimisations back into the workflow that all Build Flow users will end up utilising. Our automations are constantly updated, constantly optimised, and constantly passed back onto service users, so they can reap all the rewards of quicker, easier, cheaper construction jobs.

Clearly, just having this system, which is in a funny way the automation of automation, saves on overheads that we can pass onto you. Not only does it mean that algorithms are picking up on how to optimise a step in our workflow, but CI/CD means that these changes are instantly beamed to the rest of our system, and to you, meaning that they are instantly accessible and ready to go. This is a vital improvement for the construction sector, who normally rely on word-of-mouth contacts, manual labour, and traditional ways of operating. While there is nothing inherently wrong with these ways of doing things, they're very often time-consuming and costly. We at Build Flow want to offer an alternative, that still recognises the importance of humans and what they do, but balances that with an ingenious system that can take out all the fussy work, and improve on it day-by-day. We offer up the power of automation, and a workflow that is custom designed for people in this sector, where we've thought of the optimal way of doing something, and then tailor-made our system to fit around this.

Want to get on board with one of the most innovative companies in the contemporary construction industry? Shoot us an enquiry now to see how we can help you achieve greatness.

Photo by Alvaro Reyes on Unsplash

More from Build Flow

Get updates on Build Flow