Page Comparison

This section describes how to setup Datical project when you are using multiple branches in your development. These branches could be used for several reasons: You have

...

developers working on

...

multiple releases at the same time. You may have a branch called "release/1.0". You may also have another parallel branch called "release/2.0". 

Step-by-step guide

You will need to create multiple pipelines in your Datical project. For example, you will call them "pipeline1" and "pipeline2".

1. Each pipeline will have it's own REF database. You may also have dedicated DEV and QA databases for each pipelne. For example:
   1. "pipeline1" will look like this: REF1 → DEV1 → QA1 → STAGE → PROD 
   2. "pipeline2" will look like this: REF2 → DEV2 → QA2 → STAGE → PROD
   3. Notice that STAGE and PROD is where pipelines merge.
2. You will use these labels for your database environments:

   1. 
      

      DB Environment in Datical project	Label for the DB Environment	Notes
      REF1	pipeline1	All pipeline1 changes are deployed here
      DEV1	pipeline1 AND !abandoned AND !hold
      QA1	pipeline1 AND !abandoned AND !hold
      REF2	pipeline2	All pipeline2 changes are deployed here
      DEV2	pipeline2 AND !abandoned AND !hold
      QA2	pipeline2 AND !abandoned AND !hold
      STAGE	pipeline1 AND !abandoned AND !hold, pipeline2 AND !abandoned AND !hold	Both pipeline1 and pipeline2 changes are deployed here
      PROD	pipeline1 AND !abandoned AND !hold, pipeline2 AND !abandoned AND !hold	Both pipeline1 and pipeline2 changes are deployed here

      
      

3. Based on the table above,  When you package your changes, Daticalyour changelog.xml will include changesets for both pipelines, for example:

   1. Image Added

4. Your Datical project becomes an artifact that you publish to your artifacts repository such as Artifactory, Nexus, or artifacts repositories native to your deploy tool.
5. When you deploy your database changes using your deploy tool Datical will automatically will know what changes to deploy to each environment.
   1. For example, with the above mentioned list of changes

Related articles

...