StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>In the high demand market of web development, using CI is very beneficial and almost a requirement (now a days).</p> <p>We use TeamCity, YouTrack, Perforce and PHP Maven to build, package and deploy our web applications. The setup is as follows:</p> <ol> <li>Once developed, code is commited to the Perforce repository main folder for the app</li> <li>TeamCity is configured to check this folder for changes and build each time changes are found (see configuring TeamCity)</li> <li>Once development has reached a point where it's ready to be deployed, we integrate the main branch with the release branch</li> <li>TeamCity is configured to check the release branch for changes and deploy via FTP to the server</li> <li>Cron jobs are running on the app to deploy new releases to a QA branch</li> <li>Once changes and functionality is verified, the status of the QA deployment is set to "deploy"</li> <li>Another Cron job is running looking for new QA releases that are ready to be deployed. Once found, it extracts the package into the live folder</li> </ol> <p>In this case, our PROD and QA folders are on the same server. Alternatively, you can have multiple TeamCity build configurations that push the app to different servers (or use a teamcity to define the environment variable).</p> <p>Also, when we close tickets/issues in YouTrack, we can pull the build info from TeamCity as they interact with each other.</p> <p>Links:</p> <p>Configuring TeamCity, Maven for PHP for Joomla continuous build: <a href="http://www.waltercedric.com/joomla-mainmenu-247/continuous-build/1552-configuring-teamcity-maven-for-php-for-joomla-continuous-build.html" rel="nofollow">http://www.waltercedric.com/joomla-mainmenu-247/continuous-build/1552-configuring-teamcity-maven-for-php-for-joomla-continuous-build.html</a></p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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