Posted On Sunday, December 11th, 2011 By TobiG77
Next to Yoper, this is the project where I invest most of my time.
The idea is to write a framework for automation of software management around the work flow inherited by popular version control systems such as git and subversion. In the context of Yoper Linux this is mainly about managing rpm software packages. But trough a modular approach, that is highly focused on a well documented plugin system and how to write plugins it could be used for pretty much any software project.
Release early, release often is a well established practice to increase the quality of software. Unfortunately it comes at a price. Release management is a cumbersome process, even very well respected open source projects and software companies lack a well structured approach to release management. Time and time again you see the same bugs reoccurring again and again. Cleary those bugs could be avoided if someone would take the time to fix them. But the established release process is so time consuming and it’s considered not worthy to rock the boat. Developers put up with the flaws and those very respectable users that take their time to provide you with feedback are often faced with frequently reoccuring bugs.
The modular approach of ubuild shall allow you to write test cases and they will be automatically run through with every new release. And for the person managing the release its merely a matter of a couple of clicks on a web interface while the established routines kick in.
Ubuild is primarily meant to:
- align with well established work flows inherited by popular version control systems such as git and svn
- allow individual work flows and QA measures for each software project using ubuild
- automate many of the repetitive tasks at the right point in the process
- provide extensive documentation information of current state and how to resolve issues in a certain state
- communicate results and simplify coordination of bug tracking
- free up the developers to focus more on the fun (coding part)
- lower barriers for involvement of not so technical contributors
For the source code check out the git repository