Deploying sites from dotCMS

This guideline list out all the steps involve to deploy a site from dotCMS.

Step 1: Push Publishing from dotCMS to AWS

1. When a page/file is completed in forCMS, it needs to be saved and published.
2. Before push publishing to AWS, it is a good practice to republish the pages/files we want to push.
   • 
3. Select Push Publish to push the required files to AWS temporary folder. This folder stores all static HTML, JS, CSS, Assets exported from dotCMS.
   • 
4. In the Push Publish popup windows, select the correct branch to push to. Refer to /wiki/spaces/QA/pages/16580673 for the list of sites with their corresponding branches. The one ending with 90922 as in the sample screenshot is used for all in-house sites.
   • 
5. Once the files are pushed, the status can be monitored in Site Browser > Publishing Queue
   • 

Step 2: Deploy to Test Environment

1. To perform any deployment, you need to have access to Jenkins at http://54.191.150.142:8080/
2. When deploying to Test Environment, Jenkins downloads all the static files we pushed to Temporary AWS folder in Step 1, re-builds them to a desired structure, optimizes for performance, then upload the new files to Test bucket in AWS.
3. There are 2 types of projects in Jenkins:
   1. Projects for sites which are built with the new framework: They are listed in the homepage with, except "CMS-oldJobsManualRunner"
   2. Projects for sites which are built with the old framework: They are combined within "CMS-oldJobsManualRunner"
4. To deploy a new-framework site to Test:
   1. Select a Jenkins project in homepage, e.g. CMS-ConsciousPoker.
   2. Select "Build with Parameters" from the left menu.
      • 
   3. In the next screen, keep Deployment_Path as Test, select the desired LANGUAGEISO, then press Build.
      • 
   4. Once the process is completed, you can check the test domain, structure as test.domain.com
5. To deploy an old-framework site to Test:
   1. Select "CMS-oldJobsManualRunner", then select Build with Parameters from the left menu.
   2. Select desired site to deploy in PROJECT dropdown.
      • 
   3. Select the language folder you want to deploy in FOLDER dropdown, e.g. EN.
      • 
   4. Keep Deployment_Path as Test, then click Build.
   5. Continue to deploy pub-assets by selecting pub-assets in FOLDER dropdown. If you don't have any changes in pub-assets folder, you can skip this step.
      • 

Step 3: Deploy to Live Environment

1. Perform the same steps as deploying to Test Environment, but select "Live" in Deployment_Path dropdown.
2. When deploying to Live environment, Jenkins simply copies everything from the Test bucket in AWS over to the Live bucket. It ensures that new changes pushed from dotCMS but not yet deployed to Test Environment for verification will not get to the Live Environment.