In modern development world, many CI Tools are used for project building, testing, deploy, stats … Each Tools are specifialised for few tasks, and, in fact, most of the time it’s a good idea and they provide a well adapted set of features.
But generaly, you have only one company, one group, one team, or whatever is your organization, and so, one area of management for the project, which needs to gather information from many tools. And it’s not always easy to regroup the information.
Rules exist for that, but they are not always compliant with your way to do things. For example, many Github projects regroup information about build, test, release, as badges in top of their README page. But how could you do the same if your project is not managed with Github ? If you deploy manualy, or use an internal CI tool, how could you have the same kind of badge from various solution in one unique location ?
And the information available in this kind of readme page is not always enough for you. It’s not so easy to have distinct information for each of your project branches for example. And you may need to learn how to integrate information from various Tools.
So, here’s an idea :
- what about a new tool, easy to use, easy to install, easy to complete, which can integrate to many other by itself and gather all this kind of information and regroup it in one unique location for your needs ?
CI-LOOK is an opensource tool which tries to follow this idea. It’s currently just at the begining of its development, and no clean documentation is available yet.
So in this blog I will try to share ideas and details about the building of CI-LOOK, and build in the same time a complete documentation which for it.
CI-LOOK 