ZuloOne
English
CabinetAccount
Sign in
Menu

Ship a package

Updated

A package is a .zulopkg file: the models that change how the stand works. You upload it in Lifecycle Portal, install it on Test, mark it Ready, then release it to Production.

Note

Production takes only a package marked Ready for production. One person is not enough when the two-person rule is on: an Owner or Release manager other than the person who uploaded it must press Mark Ready for production. Lifecycle Portal is on the Business and Enterprise plans.

The portal is lcp.getzulo.com. Its buttons are in English.

How to#

To ship a package, sign in at lcp.getzulo.com and open the tenant. In the left menu, under Asset library, open Packages.

Under Upload a package, choose the .zulopkg file. Press Upload. The portal checks every file against the list inside the package before it keeps it. If that exact version with the same contents is already there, the notice is This exact package was already in the library.

Open the package row. The page is titled with the package id and version. Under On the road to production:

  1. 1 · Install on Test. Pick Environment (a running Test, or Development). Press Install. The portal validates first, takes a snapshot, installs while the stand runs, and rolls back if the models do not compile. Then the package's own tests run there. A successful Test install with tests green is what a Ready mark rests on. A Development install changes nothing for that mark.
  2. 2 · Ready for production. When Test is green, a second person presses Mark Ready for production. If you uploaded the package and the two-person rule is off, the mark is stamped self-approved and stays so on the history.
  3. 3 · Release to production. Type the version to confirm. Press Release plus that version. Production is validated, snapshotted, then installed; it rolls back if the models do not compile.

If there is no Test yet, the install step says No running Test or Development environment. Deploy one.

Release settings in the left menu shows whether the two-person rule is on or off.

A Ready mark that should not go live: Withdraw the mark, with a reason.

Example

  • File acme-sales-1.4.0.zulopkg
  • Upload
  • Environment acme-test (Test)
  • Install — tests 12/12
  • Second person: Mark Ready for production
  • Type 1.4.0, press Release 1.4.0

Production now runs 1.4.0. The Test stand still has it too.

Tip

Take a backup of Production before Release if you want your own restore point — Back up an environment. The portal also takes a snapshot itself before the install.

If the command refuses#

What you see What to do
No running Test or Development environment. Deploy a Test environment, wait until it is running, then Install.
Production takes only a package marked Ready for production. Finish the Test install, then Mark Ready for production.
The Ready button is missing and the page names the uploader The two-person rule is on. Sign in as a different Owner or Release manager.
rolled back on History The models did not compile on that environment. Fix the package, upload a new version, install again.
This package carries no tests. The mark signs an install that compiled. Add tests to the next package if you need them on the mark.
Refused on Packages after Upload The file failed the check (manifest, model.json, size). Ask whoever built the .zulopkg to rebuild it.

See also

Was this page helpful?