Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p><strong>What distinct servers exist with respect to the development process? What is their purpose?</strong></p> <ul> <li><strong>SCM Server</strong> e.g. SVN, Git, CVS - central source repository, usually internal access only.</li> <li><strong>CI Server(s)</strong> e.g. CruiseControl, Hudson - Continuous Integration server for automated builds/testing.</li> <li><strong>FileServer</strong> e.g. Samba, Shared Windows directory - for storing built artifacts, sharing downloads between the development team</li> <li><strong>Test/Staging/Production</strong> servers - machines built to the same spec of hard/software for running your actual application.</li> </ul> <p><strong>Where is your master source repository?</strong></p> <p>Usually internal access only, can share this machine with another purpose e.g. CI.</p> <p><strong>Where is development work done?</strong></p> <p>On each developers local machine is best, then integrate changes via SCM and CI.</p> <p><strong>Where is testing done?</strong></p> <p>Usually on a server set aside for testing. Normally there is a set of environments and builds are promoted through each stage as they pass testing:</p> <ul> <li>Test machine - for checking out builds, usually mirrors the setup of a devlopers machine.</li> <li>Staging machine - for builds that pass the basic tests - this server will be more of a mirror of the live production system.</li> <li>Pre-live - An optional server which will be given to business users to test before the server goes fully live.</li> <li>Live/Production - builds are promoted to this server when they have been accepted by the testers and the business.</li> </ul>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload