Describing a very minimal scenario I want from CI as a service
I want some one to build CI as a service for .NET. Actually, I want to build it myself, but I'm not allowed to. What would it look like? Let's take the simplest useful scenario I can think of: building a class library that is delivered as a NuGet package.
I go to http://ciaas. I create a new project. I point it at my GitHub repo. It spends a few seconds looking at my repo. It sees that I have a few things there it knows how to build: a .sln file, an .msbuild file, some .csproj files, some .ps1 scripts. I choose the .msbuild file.
It shows me a list of the targets in the file (or maybe just lets me type in the target I want to run). It starts a build so it can show me the output. I chose the output files that I want to make available as artifacts (in this case, the .dll files and the .nupkg files). I have a URL I can give to folks that shows builds, status, and where they can download the artifacts.
ciaas emails me when there are problems. It has feeds for people to subscribe to.
Keep in mind this is the most trivial, useful scenario I can think of. I'd need far more features for most of the "real" projects I have.