Every zendev environment has a copy of the platform-build repository and knows how to build Zenoss using the environment’s source tree. This is, in effect, the new Zenoss build system.
This should (currently) only be attempted on the provided Fedora base box. Simply issue the command:
zendev build srcbuild
Since zendev already set up ZENHOME to $(zendev root)/zenhome, that’s where it will end up.
Although Zenoss will be built using the environment’s source tree, zendev does NOT currently symlink Products/bin from the source tree into $ZENHOME, a common development environment practice. Contributions welcome.
The only requirement to build RPMs is Docker. zendev will create a Docker image that can build an RPM, mount the appropriate source directories, build the RPM, and copy it to an output directory mounted from the host.
# Build Core (+ core ZenPacks)
# Make sure you have necessary repos (first time only)
zendev add $(zendev root)/build/manifests/{core,zenpacks.core}.json
zendev sync
zendev build --clean core
# Build RM (Core + ZenPacks).
# Make sure you have necessary repos (first time only)
zendev add $(zendev root)/build/manifests/{core,zenpacks.core,zenpacks.commercial}.json
zendev sync
zendev build --clean resmgr
Passing --clean to zendev build will run make clean in the build directory before running the build, which might be necessary to pull in repositories you’ve synced.
Passing --output or -o with an argument will cause any build artifacts produced during the run to end up in the directory specified; the default is $PWD/output.
zendev can build from a manifest other than your current source tree. In this case, it will perform a shallow clone (last commit only) of all the repos into a temp directory, then build the specified artifact from that.
# Build from a local manifest
zendev -n build core -m /path/to/manifest.json
# Build from a remote manifest
zendev -n build core -m https://dl.dropboxusercontent.com/u/784231/manifest.mf
# Build using source from several manifests
zendev -n build core -m /path/to/manifest1.json http://host/manifest2.json
# Build from a manifest tag
zendev -n build core -t nightly-build-123