ZuloOne
English
CabinetAccount
Sign in
Menu

Open Lifecycle Portal

Updated

Lifecycle Portal is the desk for the stand: Production, Test and Development, the package library, backups, who may sign a release, and the credential a pipeline uses. Office work stays on the stand. Shipping a change to Production happens here.

Note

The portal is on the Business and Enterprise plans, at lcp.getzulo.com. A smaller plan still has the stand; this desk is on those two. The portal is in English even when the office stand is not.

You do not edit Production by hand. A change is a .zulopkg file. It is installed on Test first. Mark Ready for production is a second person (Owner or Release manager, not the uploader) unless Release settings turns the two-person rule off. Then Release plus the version puts it live. Production has no rebuild-or-delete button.

A pipeline may Upload and Install on Test. No CI scope marks Ready.

How to#

To open Lifecycle Portal, sign in at lcp.getzulo.com. Pick the tenant. The left menu is the map:

  • Overview — plan, your role, Production, and the Test and Development stands beside it (the plan caps how many).
  • Environments — the same list, grouped by project. + Deploy an environment makes a Test or Development stand: empty, or a copy of Production with mail and outbound jobs off.
  • Asset library → Packages — upload a .zulopkg, then ship it: Install on Test, Mark Ready for production, Release.
  • Asset library → Database backups — copies you took with Back up now. Restore onto Test or Development only. Copies Zulo took before an upgrade or an install sit under Taken by Zulo and do not count against the limit.
  • People and roles — an Owner invites by e-mail. Roles: Owner, Release manager, Developer, Viewer. A tenant always keeps at least one owner.
  • Release settings — two-person rule on or off. Off stamps self-approved on the history.
  • CI credentials — what the pipeline uses to upload and to install on Test. Ready stays a person's act.

On an environment page you can Restart, Stop, take a backup, read Logs (newest first, even when the stand is stopped), and Run tests (a run rolls back what it writes). Development can Open the workspace so a laptop mirrors the folder. Updates from Zulo snapshots first and tells Production to update a Test stand first.

Example

Tenant acme. Overview shows Production acme.zulo.one and Test acme-test. A developer Uploads acme-sales-1.4.0.zulopkg, Installs on acme-test. A release manager who did not upload presses Mark Ready for production. Then Release 1.4.0.

Tip

Grant a role on the office stand (ribbon Administrator) is not this page. Portal roles decide who may ship. Office roles decide who sees lists and cards.

If the command refuses#

What you see What to do
No tenant in the list This login has no portal role yet. Ask an Owner to invite you.
Left menu has no Packages This desk is on Business and Enterprise. A smaller plan still has the stand.
+ Deploy an environment is missing The plan quota is full, or this role cannot deploy. Delete or redeploy a Test/Development stand, or ask an Owner.

See also

Was this page helpful?