What It Does

Whenever you compile a component in JCB, it generates a build ID that includes:

• The semantic version (e.g. 1.2.4)
• A unique hash or timestamp
• A reference to the compiler and JCB version used

This build ID is:

• Embedded into the component’s manifest XML
• Shown in the JCB compiler UI
• Optionally injected into the codebase as a constant or variable

Where It Appears

• In your component’s manifest.xml file (as version, build metadata, or changelog)
• In the JCB backend under Compiler → Build Summary
• Inside the compiled PHP files (e.g. defined constant or injected comment)
• Optionally written into logs, dashboards, or update server metadata

Why It Matters

• ✅ Traceability: Every package has a traceable identity, even if its version number hasn’t changed. You can always determine which compile produced which output.
• ✅ CI/CD Integration: Automate deployments with confidence, using build IDs to tag releases in Git, on update servers, or in changelogs.
• ✅ User Support: Support teams can instantly identify what version and build a customer is running — even if manually modified.
• ✅ Multi-Version Awareness: For J3, J4, and J5 builds, each version-specific compile will include its own build ID — helpful for maintaining compatibility without confusion.

Configuration Options

In JCB you can:

• Enable/disable build ID generation in the compiler settings
• Choose a format (e.g. timestamped, UUID, hash of source)
• Set naming conventions for output ZIP files (e.g. mycomponent_1.2.4+build20250702.zip)
• Include/exclude build metadata in source comments

Use Cases

• 🔁 Daily builds with unique IDs for QA teams
• 📦 Nightly builds for public testing
• 🌐 Publish build ID to update servers or changelogs
• 🧪 Compare builds even when version numbers remain the same
• 🛠️ Restore or rollback to a specific build in distributed environments

Best Practices

• Keep build ID tracking enabled for production builds
• Use semantic versioning + build metadata for clarity
• Store build IDs alongside Git commits or packaging logs
• Display the current build ID inside the component’s About screen

Conclusion

Version-aware build IDs are a subtle but powerful feature that bring professionalism, reproducibility, and clarity to your component lifecycle. Whether working alone or in a team, they help ensure that every package you release is identifiable, verifiable, and maintainable.

Summary

JCB automatically generates unique build identifiers that are tied to the version number and timestamp of each compiled package. This ensures traceability, reproducibility, and clarity in distributed builds — especially across teams, environments, or CI/CD pipelines.