Check, build and publish

What you're doing

Taking a plugin from "it exists" to "installed in my tenant", with a safe way back at each step.

Validate -> Snapshot -> Compile / test -> Build -> Publish (install) -> Roll back if needed

Validate

Header Validate (or Build menu). The chip shows Valid, N warnings or N errors. Click it to open Problems; each problem opens the screen it is about.

Snapshot

File, Save snapshot... stores the whole source under a name. File, Restore snapshot... brings one back (it snapshots the current state first, so a restore can be undone).

Compile and test code (only if the plugin has code)

From Build: Compile Java, Run Java tests, Package Java; for Node: install, run tests, build. Output appears in the Output panel. To add a Java backend: Build, Add Java backend (starter). See Backend services.

Publish

Deploy, Publish... runs these in order and stops at the first failure: check for problems, snapshot, compile/test/package Java, install/test/build Node, make the version new (raises the patch number if already installed), build the package, fetch it, install it for this tenant. A failed step names itself, shows the error lines and offers Restore snapshot.

Roll back

• Not yet installed: File, Restore snapshot....
• Installed: Deploy, Roll back installed version (one version back).

Move plugins around

• File, Export plugin as .zip; Import plugin (.zip / .spk) (refuses an existing id).
• Save as / Clone copy under a new id (only id and name in plugin.json change).
• Edit, Plugin properties...: name, version, description.
• Environment promotion moves published artifacts between environments.

Where builds run

Each build runs in a fresh, isolated container that is deleted afterward; nothing builds inside the ERP backend. A build is killed after 15 minutes. Maven works offline against libraries baked into the worker image.

Check it worked

The header shows Installed and the plugin's menu entry appears on the launcher.

Common mistakes

You see	Fix
403 on a build or publish call	assign the account the Studio Staff role
Sent back to the login page	assign the Studio Staff role
"the build service refused the job (503)"	two builds are running; wait a moment
"package ... does not exist" on compile	the library is not in the worker image; use the platform API
Publish stops at "Make sure the version is new"	tick Raise the version automatically or raise it in Plugin properties