VCS organization for CI, D & D

  • Our shop has four main environments: Development, System Integration, User Acceptance and Production. I understand that some shops have fewer environments and others more.

    At any given moment, these environments differ as new applications and databases are developed and existing ones are enhanced. Pretty normal I think.

    What I'd like to know is this:

    What is the best way to organize source control?

    One source tree or four?

    If one source tree, how can you easily show the current state of a given environment at a given point in time?

    If four source trees, how do you record and track the progression of a new app or change through the four environments?

    Gerald Britton, Pluralsight courses

Viewing 0 posts

You must be logged in to reply to this topic. Login to reply