Building Compatible Bigtop Components for Ambari 3.1

Ambari 3.1 packages require a deliberately selected compatible Bigtop reference. Ambari 3.1 is not a Bigtop release and must not be described as Bigtop 3.1.

Select the Stack reference

Check service definitions and release issues for the supported Bigtop Stack reference. Bigtop 3.4 inherits from the 3.3 and 3.2 lines; choose and record the exact compatible ref or tag.

Verify source roots, RPM profile, required JDK, Python interpreter, package manager, and platform support. Do not copy an HDP or CentOS 6 recipe without checking current dependencies.

Build and validate

Clone Bigtop at the selected ref and inspect its current instructions. Keep the Ambari source tag and Bigtop ref as separate provenance fields. Build only required components and capture output, package names, checksums, and configuration.

Install packages in a disposable Ambari environment. Verify registration, configuration, startup, upgrade, and failure recovery, then run focused Server, Agent, UI, and telemetry tests.

Report build or integration errors with source and compatible-ref evidence; never change the claimed Stack version to make a build appear successful.