System jobs and run history only — inventory / host-facts crawls when registered.
| Job id | Next run | Trigger | Function | Source |
|---|---|---|---|---|
Open this tab to load jobs… | ||||
| Run id | Job id | Scheduled (UTC) | Finished (UTC) | OK | Summary |
|---|---|---|---|---|---|
— | |||||
| Name ⇅ | OS ⇅ | Version ⇅ | Last Logon ⇅ | Status ⇅ |
|---|
| Name ⇅ | Type ⇅ | SQL ⇅ | Env ⇅ | CST ⇅ | Cert expiry ⇅ |
|---|
Application services
Catalog from deploy config. Components restart via IIS (W3SVC) or their Windows services.
| Component ⇅ | Env ⇅ | Server ⇅ | Code path ⇅ | Service / IIS ⇅ | Status ⇅ | Startup ⇅ | Actions |
|---|---|---|---|---|---|---|---|
| Loading service catalog… | |||||||
—
Maintenance · Code roll
Software deployment
Import a PSN build from SFTP, verify it is what you think it is, then roll it to stage or production — with instant rollback and automatic email notifications.
—
Waiting for the SFTP listing
—
Nothing imported yet
—
No pending schedules
—
No deployment logs found
Automation
Automatic stage deploys
Every 30 minutes Helix checks SFTP for newer builds of components it has rolled to stage before. Once a new upload is stable it is imported, validated and scheduled to stage 15 minutes out — the entry appears under Scheduled rolls below and can be cancelled there. A version that is rolled back, cancelled or fails repeatedly becomes manual roll only and is never auto-scheduled again. Rolling that version to stage yourself clears the flag, even if you roll it back afterwards. Production is never touched.
Loading automation state…
Step 1
Import the build from SFTP
The newest uploads on the SFTP server, grouped by component. Click Import next to the file you want to roll — Helix downloads it and verifies the zip. Anything Helix does not recognise is flagged below and cannot be rolled.
| Component · SFTP folder | Newest files on SFTP (up to 3 — import an older version to roll back a release) |
|---|---|
| Loading the SFTP catalog… | |
Step 2
Confirm what you imported
Select the imported file, declare which component it is and where it is going, then Validate. If the file does not match the declared component — wrong name or wrong contents, e.g. an “Admin2” drop declared as Admin — Helix refuses to roll it.
| File | Version | Looks like | Downloaded | By | Clean up | |
|---|---|---|---|---|---|---|
| Nothing imported yet — use Step 1 first. | ||||||
Step 3
Roll now, or schedule it
Both buttons unlock once Step 2 validation passes. Production requires a CR number. The roll stops the component, swaps the code folders, and starts it again — the version that was live stays on the server for instant rollback.
Run Jenkins
QA
Runs the Jenkins job eci.PSN - Smoke Testing against stage or production without deploying anything. Helix starts the job, polls Jenkins until it finishes and shows the result below. Every roll also runs this job when it finishes: if that run fails, the roll is rolled back. A run started here never rolls anything back.
| Environment | Result | Jenkins build | Duration | Run | When |
|---|---|---|---|---|---|
| Loading QA results… | |||||
Roll back options
Live is what is running now; Previous is the version kept from the last roll — Roll back swaps back to it in seconds. Folders deployed before Helix show as “pre-Helix” until their first Helix roll.
| Component | Host | Live | Staged (ready to roll) | Previous (rollback) | Action |
|---|---|---|---|---|---|
| Loading roll back options… | |||||
Scheduled rolls
Upcoming and recently finished scheduled deployments
| When | Component | Env | Version | Deploying in | By | Status | |
|---|---|---|---|---|---|---|---|
| None. | |||||||
Recent Helix deployments
Rolls and rollbacks run through Helix, newest first (up to the last 400)
Loading…
Website
—
Server
—
