This sounds like your testers might get their sessions pulled if they're testing while someone triggers a new build.
It's considered a good practice to provide a certain level of stability in an environment with manual testing ongoing. In practice this often means that you need two environments or installations - one used by the CI machinery and another for testing where the latest successful build is installed, say, every night at 3am. This way the test engineers can rest assured that nobody's going to pull the carpet on them during the day.
Originally posted by kalyen kumar: ISSUE :If a code commit is done and a rebuild is going on......at the same time if some one triying to test it.
Does this break the system.......i am afraid and wanted to know in advance how does the system react to this.
I just realized that I may have answered to a different question that was asked. Did you mean that you're concerned 1) whether a new build will screw up ongoing testing, or 2) whether a tester will screw up the new build by clicking on the application while the new build gets installed?
I already answered 1) but if you meant 2) then I'd say it's unlikely but impossible to say for sure without knowing more about the application and its implementation.
I second Lasse's recommendation: have the fitnesse environment separate from the CI environment. The last step of the CI build could be to automatically update the fitnesse environment with the current version.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
He puts the "turd" in "saturday". Speaking of which, have you smelled this tiny ad?