JUBELBUILD — DEVELOPER TOOLS
Versioning
Step 2 · Set the target version and let the transformation engine build all three variants.
Analysis done — ready to build
Once your master ZIP passes analysis, the system is ready for the build. You define the target version for this specific build — leave it as is to keep the version detected during analysis, or override it.
The transformation engine
When you click Start Build, JubelBuild runs the full pipeline automatically:
- Stable-tag sync: the
Stable tagin yourreadme.txtis updated to the target version. - Tag removal: for the FREE version, every code block enclosed in
[PRO]tags is physically removed from the files. - Debug-log removal:
file_put_contents(…debug.log)calls are removed from FREE and PRO builds. - Addon-subfolder removal: subdirectories that carry their own Plugin Name header are stripped from FREE and PRO — WP.org allows only one plugin per ZIP.
- WP.org compliance: all 18 WordPress.org plugin guidelines are applied automatically to the FREE build.
- PHP syntax check: if Parallel Lint is active, all three builds are validated for parse errors before packaging.
- ZIP packaging: clean archives are created for every build variant.
Set the version, start the build
One click turns your DEV source into clean DEV, FREE and PRO archives.
