Pre Central Deployment Tasks

Pre Central Deployment Tasks

Pre Central Deployment Tasks

Objectives

Complete necessary pre-deployment tasks

Prerequisites

Access to Redmine

Access to production application server

Access to Subversion

Access to TeamCity

Instructions

Update Semantic Version Information

Create subtask for updating Selenium tests

  • Create subtask under Redmine task for the release to have Selenium UI tests updated.

Run Selenium UI Tests on TeamCity

  • In TeamCity, run Back Office UI tests against the development environment for regression testing purposes.

Review SQL Scripts with Database team

  • Meet with a member of the database team prior to the release to review database script changes related to the release.

Schedule and hold release meeting

  • Release meeting should be held in the week prior to the release. This meeting will be with all operations team members to discuss upcoming features and bug fixes.

Complete all testing

Review code checked in for the upcoming release

Coordinate updating the status page for scheduled maintenance with Brett on the date of the release meeting

Stage war files on production server

  • Upload war files to the home directory of your user on the production server for staging.

Create tags in subversion for each project updated

  • Create subtask under Redmine task for the release to have tags created.
  • Identify all projects updated during the release and create a tag from the HEAD version with the version number.

 


    • Related Articles

    • Post Central Deployment Tasks

      Post Central Deployment Tasks Objectives Complete necessary post-deployment tasks Prerequisites Access to Redmine Access to production database Access to fcadmin Access to deployment test server Instructions Send release docs Release docs are located ...

    • Central Deployment Process

      Run SQL scripts in http://sourcecontrol.fullcount.net/repos/internal/trunk/at-fullcount-model/src/main/resources/sql/nextDeploy Pause TeamCity test for fullcount-uptime-production-overnight. Download release war file from archiva for all ...

    • Remote Deployment Process - Java

      Deployment Process Determine if a valid argument has been passed in Only continue if downloadOnly, postDownload, fullDeployment, handleSuccess, checkHash, verifyApplications passed through. Lock file to stop deployment from running more than once ...

    • Run Remote Deployment Process - Java

      Remote Server Configuration This has already been completed for all existing remote servers. Java 1.8 installed Tomcat located at /srv/tomcat XE database installed and running with fc_obj_owner user Directory /home/deployment exists Database backup ...

    • Overview of Deployment Process for Remote Servers

      Overview of Deployment Process for Remote Servers Introduction The process for updating the Touchscreen and Back Office applications is known as the deployment process. The deployment process is only used for updating applications and databases on ...