Originally I developed against a custom, private csharp backend that would connect to Team Foundation Server and fetch whatever is needed for the build monitor. Since I cannot release the source code to that, the monitor is not usable as a stand-alone application.
To this end, I should consider supporting Github and Travis CI instead. Github would provide version control history, and Travis would obviously provide build statuses and history.
An interesting idea that I'd like to try out is removing the need for an explicit backend altogether.
This would reduce the dependencies of running build-monitor massively
If everything could be ran in the browser, could (in theory) provide links to every existing Github + Travis project that is publicly available. This could be extremely useful for a lot of people!
Default configuration for repositories could be to show all builds in the matrix. A hard-coded file in the repository root could be made to provide default configuration.
Originally I developed against a custom, private csharp backend that would connect to Team Foundation Server and fetch whatever is needed for the build monitor. Since I cannot release the source code to that, the monitor is not usable as a stand-alone application.
To this end, I should consider supporting Github and Travis CI instead. Github would provide version control history, and Travis would obviously provide build statuses and history.
An interesting idea that I'd like to try out is removing the need for an explicit backend altogether.
Reference: https://developer.github.com/v3/ https://docs.travis-ci.com/api