Databases
StackOverflow2013
Postsdbo
POBest-practice for continuous integration and deployment
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POBest-practice for continuous integration and deployment
    primarykey
    data
    text
    <p>Continuous integration concept has just been integrated in my team.</p> <p>Assume we have an integration branch named <strong>Dev</strong>. </p> <p>From it derived 3 branches, one for each specific current project :</p> <ul> <li>Project <strong>A</strong> </li> <li>Project <strong>B</strong></li> <li>Project <strong>C</strong></li> </ul> <p>First, Teamcity is configured on a dedicated server and it goals is :</p> <p><em>Compiles and launches unit and integration tests from versioned sources from each branch including Dev</em></p> <p>Then, of course, each project branch (A,B and C) must be tested in a cloned production environment so that UAT can be carried out.</p> <p>But I wonder what frequency should we deploy on? Everytime a source code changes ?</p> <p>Should we deploy only Dev that contains mix of the 3 projects after merging each one to it (corresponding to the reality in next production release) or the 3 projects independently?</p> <p>If Dev is deployed, potentially future changes on Dev must not be taken in account. Indeed, there might be a new project starting called <strong>Project D</strong> and that mustn't be part of the next release. So taking Dev for integration (UAT) is risked because deployer could unvoluntary integrate content of Project D and so environment will not reveal the reality of the next release.</p> <p>Other solution: we're not taking Dev but independently the 3 projects, so must there be 3 cloned production environments in parallel? </p> <p>If yes, UAT couldn't be reliable since behaviour of integration environment might change very often...</p> <p>Concept of continuous deployment for UAT isn't clear for me... </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USRoman C
    1. USMik378
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POBest-practice for continuous integration and deployment
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POBest-practice for continuous integration and deployment
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POBest-practice for continuous integration and deployment
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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