Back to Home

Releasing Manually

Table of Contents

Dev

On your local machine do the following:

  1. Run gulp releaseDev in git bash from the repo containing the code you need released. This will create a release folder.
  2. Copy the generated release folder to an external hard drive.

On your Cigna machine do the following:

  1. Plug in the external hard drive.
  2. Run any necessary Script for Release files.
  3. Run release/sql/createAllButTables.sql.
  4. Copy files in release/files into webroot. Do not copy folders. Only copy files in folders if the files have changed. Note: if you cannot see the release directory in the file explorer, navigate to the "View" tab, then click "Show selected items".

  5. If any ssis files have changed, navigate to the ssis subdirectory and individually move changed packages, config, excel, and tws files to the correct shared drive or other location.

    NOTE: Drop sample projects sometimes require updates to their macro enabled (.xlsm) file. This file is purposefully not added to the release folder, as moving it via flash drive tends to corrupt it. This file must be moved to the Cigna environments via email.

Staging

(Visual Studio 2019 is a requirement) (Make sure msbuild is added to your path)

On your local machine do the following:

  1. Run gulp release-staging in git bash from the repo containing the code you need released. This will create a release folder.
  2. Copy the generated release folder to an external hard drive.

On your Cigna machine do the following:

  1. Plug in the external hard drive.
  2. Combine any necessary Script for Release files and release/sql/createAllButTables.sql.
  3. Send resulting file to Bud with a backout script.
  4. Copy all files in release/compiled into webroot.
  5. Copy all files in release/compiled/bin.
  6. What to do for ssis files?