Databases
StackOverflow2013
Postsdbo
POReleases with multiple long lived branches using maven
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POReleases with multiple long lived branches using maven
    primarykey
    data
    text
    <p>So here's the Subversion, Jenkins, Beanstalk setup:</p> <ul> <li>trunk/ -> development main line <ul> <li>CI builds on checkin</li> <li>Successful CI build spawns CD build that pushes to "Testing" Beanstalk environment</li> </ul></li> <li>branches/qa/ -> current release candidate <ul> <li>CI builds on checkin</li> <li>Successful CI build spawns CD build that pushes to "QA" Beanstalk environment</li> </ul></li> <li>branches/prod/ -> current release <ul> <li>CI builds on checkin</li> <li>Successful CI build spawns CD build that pushes to "Prod" Beanstalk environment</li> </ul></li> </ul> <p>Basically what I want to do is this:</p> <ul> <li>Development cycle starts in trunk (trunk: 0.1-SNAPSHOT)</li> <li>When development cycle is complete branch to qa and being qa cycle. Also begin next development cycle in trunk (trunk 0.2-SNAPSHOT, qa: 0.1-SNAPSHOT)</li> <li>When qa cycle is complete branch to prod and perform maven release. Also begin next qa cycle (trunk 0.2-SNAPSHOT, qa: 0.2-SNAPSHOT, prod: 0.1)</li> </ul> <p>The idea is to have short sprints where at the end of each a development cylce ends and a qa cycle begins. When the qa cycle is complete it is pushed to a production environment.</p> <p>I'd like to preserve the branches and do merging to\from the branches instead of deleted and re-created. The idea being that any fixes made in qa would be merged back intro trunk, and any changes made in prod would be merged back into qa (and back into trunk).</p> <p>prod is therefore a "hot" branch and represents the current state of the production environment.</p> <p>this is for a small team of developers working on week long sprints.</p> <p>Questions:</p> <ol> <li>How does this setup sound?</li> <li>Can i get maven to act correctly, or will i need to script this?</li> <li>Who is your daddy? And what does he do? </li> </ol>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USBrian Dilley
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POReleases with multiple long lived branches using maven
      1. USBrian Dilley
      1. VTBountyStart
    2. VO
      singulars
      1. POReleases with multiple long lived branches using maven
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POReleases with multiple long lived branches using maven
      1. USPreet_Android
      1. VTFavorite
    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