ECinteractive
Helix ECinteractive Product
Servers —
Name ⇅ OS ⇅ Version ⇅ Last Logon ⇅ Status ⇅
Websites —

Name ⇅ Type ⇅ SQL ⇅ Env ⇅ CST ⇅ Cert expiry ⇅
Code Roll —

1 — Dev drop — available versions

Devs drop release zips here. Helix lists this folder via UNC from eci-prod-data, then you pick a version to copy onto eci-prod-data. If stage finds a problem, use Remove from eci-prod-data to delete that release and its prepare slots before importing a fix.

Dev drop (UNC)
—
Same path by IP
—
Version Name Type Size Modified (UTC)
Loading available versions from dev drop…

2 — Refresh stage databases

Restore production database backups onto stage SQL, then run the sanitize script. Run manually before a stage code roll when databases need to match production.

—

    3 — Target environment

    Choose stage or production before you prepare components and roll. The same environment applies to prepare (step 4) and roll (step 5).

    Target environment:

    —

    —

    4 — Extracted builds (on eci-prod-data)

    After download, web/service folders are published under E:\Powershell\Code as - new prepare slots. SQL and CDN stay in the version extract folder — select the release and use the SQL/CDN checkboxes, then prepare at the bottom of this section.

    —

    Release folders

    Version Manifest Prepared Rolled Components Modified (UTC) Actions

    Release components (SQL / CDN) — from extracted version folder

    Pick the active release above. SQL copies scripts to C:\temp\{version} on Prepare and runs *.sql in numeric order on Roll. CDN merges CDN_update into the image server on Prepare.

    Component Source folder Status
    Select a release folder with a manifest.

    Prepare slots (- new on eci-prod-data) — select components to stage

    Folder Modified (UTC)

    Local zip copies

    File Size Modified (UTC)

    Fan-out selected components to each target server's - new folder for the environment chosen in step 3.

    5 — Roll prepared code

    After step 4 completes, review what is prepared below. Roll now or schedule for later (uses the target environment from step 3). If - new folders were removed on servers, use Clear prepared state so the tracker matches reality.

    Prepared for roll

    Nothing prepared yet — complete step 4 first.

    Roll back to previous version

    Each roll leaves the previous version beside the live folder as - old. That copy survives only until the next roll of the same component replaces it, so check first. Rolling back stops the service or IIS on the host, swaps the folders, and starts it again — the rolled code becomes the new - old, so you can re-apply it.

    Website

    —

    Server

    —