You may notice that I stick to original project name at the end of the day,
even thought I wish to change it. That happened for 2 reasons: first, I
really get used to candidate and it’s good enough project name.. second, I
spent some hours of brainstorming but found out nothing better that
This weekend I also finally concluded project web site and hosted it as
github pages -
http://alexbeletsky.github.com/candidate/. So, ladies and gentlemen - please welcome,
is ready to be shown to the world.
Thinking about nearest “competitors” in this area I would re-call
Paul Stovell. Octopus uses
Build Server / Tentacle (Agent) architecture principal, while Candidate is
simple Agent architecture - you host it the same machine as your environment
is (stage, production) providing both integration and deployment
My goal is stabilize and improve Candidate through this year, so it fulfill
different requirements including performance and scalability. I switched all
my projects to use Candidate now, so it would give me some initial
Following the principle “Build product X to learn technology Y” I’m going to
proceed with Candidate to shape following areas that I wish to improve
Technological stack is still ASP.NET MVC3 / C#/ jQuery. Currently
application requires to be hosted on IIS, with application pool Process
Identity equals to Admin. This does not suite all users. So, I’m looking
forward to create self-hosted version using
I also try to target UI / UX issues as much as possible.
I would be happy to. I’ll much encourage you to download application,
install it, perform simple testing (scenario could be found
here). Let me know what you think, that would be great initial contribution. As
for any github hosted project, you are absolutely free to fork, hack it out
and send pull request.
Thanks for you help.