Practicing TDD and working with a Continuous Integration system is great but context switching between the command line to check the status of my builds is annoying - enter ci a tool for checking the status of your builds right in the command line.

Basic usage cic --server http://jenkins.domain.com

cic takes configuration parameters on the command line or configuration files places on the current path.

Take a look at the github pages for this project.

OS-X Binaries are available here: http://download.umisiri.com/ci-console/

cic uses a set of configuraiton files to know what to do. It assumes that you have some sort of project hierachy on your filesystem.

cic assumes that you have a filesystem something like

projects
       `- project1
       `- project2

Assuming that project1 and project2 are built by the same ci system you will want to define that connection by having a .ci file in the projects folder.

.ci files are currently in json format and should not be checked in to version control because they contain continuous integration server credentials.

{
    "server" : {
	"type" : "jenkins",
	"url" : "http://jenkins.example.com",
	"username" : "[email protected]",
	"password" : "my password"
    }
}

Hudson and Jenkins are currently supported server types.

> cic