Stormwind Project - AT LAST
I´m thrilled to announce that the
Stormwind Project Community was born.
It has been an intense work for both me and Cláudio Figueiredo (BTW buddy, A HUGE THANK YOU!!!).
Even being so much work, it´s been REALLY rewarding to watch as the community takes shape. It´s really a wondrous thing having some idea in your head become something real, something that people can discuss.
Right now we have the project portal setup and we are incrementally adding content to it. There´s a very good ammount of content already there as of today, but we´ll be adding project-specific content during the week.
After stabilizing the portal, our next move is to have the Build Server online. Since WebHost4Life won´t support it in the near future and we really need a build server we came up with an idea on how to integrate a remote build server and our DotNetNuke(DNN) portal:
- We build a Service (WCF likely) that retrieves and stores information on builds (results, files, etc).
- We build a publisher to CruiseControl that uses the above Service to publish the results of the build to the Portal.
- We build a DNN module that reads the data stored by the Service in some shared repository.
What do you guys think? Is this feasible? Is there some better way of doing it?
After the build server is stabilized we´ll have to configure CI for each project. This should take some time to become functional.
Then we´ll start again on the development of new releases for each of the projects (NMVP 1.0.0, ValEver 1.0.0, Digital Fortress 0.1.0, Stormwind Reports 0.1.0).
Hope to get some feedback from you guys real soon.
#121