manageiq/rpm_build repository overview

⁠ManageIQ RPM Build

⁠Summary

This repository contains code to build RPMs for ManageIQ appliances and container images.

It performs the following tasks:

• Clone source repos
• Run bundle install, compiles assets for UI and a few other tasks needed
• Create tarballs
• Build RPMs (locally in the container image or in Copr)

⁠Output

It produces the following rpms:

• /usr/lib/systemd/system/ contains systemd service files.
• /var/www/miq/vmdb contains application files.
• /opt/manageiq/manageiq-appliance contains files linked into /etc/.
• /opt/manageiq/manifest contains manifests.

⁠Steps

⁠Obtain container image for building RPMs

You can either download the latest build image or building a new one locally:

• docker pull manageiq/rpm_build:latest
• docker pull manageiq/rpm_build:latest-jansa
• docker build --pull --tag $USER/rpm_build:latest .

Typically the first example works best but if you are modifying which files end up in the rpm, the third example is the one you want.

⁠Building a release

The github tag/branch is passed on the command line e.g.: --git-ref jansa. A few other options and explanations are availabe in build.rb⁠ for the basic installs.

docker run --rm manageiq/rpm_build:latest build --git-ref lasker --update-rpm-repo

For older builds, the git-ref is already stored in config/options.yml and not necessary.

docker run --rm manageiq/rpm_build:jansa-3 build --update-rpm-repo

⁠Building a custom release

Sometimes it is necessary to build rpms with code from pull requests. This explains how to do that.

⁠Defining build parameters

The options.yml⁠ points to the appropriate repos and tag/branches.

A typical options.yml will only override the source and the refs. This example uses branch feature1 from kbrock's github repo:

mkdir OPTIONS
vi OPTIONS/options.yml

---
product_name:      manageiq
repos:
  ref:             master
  manageiq:
    url:           https://github.com/kbrock/manageiq.git
    ref:           feature1
  manageiq_appliance:
    url:           https://github.com/kbrock/manageiq-appliance.git
    ref:           feature1

The option file is brought into docker by mounting the directory with -v $(pwd)/OPTIONS:/root/OPTIONS

⁠Using a custom NPM registry

Any of the keys in options.yml⁠ can be overridden.

• If overriding the NPM registry, set the npm_registry key in the options.yml.
• If building RPMs in Copr,
  • set the rpm.repo_name key in the options.yml.
  • run the container image with -v <copr token file>:/root/.config/copr.
• If updating the RPM repo it would be helpful to attach a volume to hold the RPM cache with -v <dir>:/root/rpm_cache. Any RPMs not in the cache will be downloaded to the cache first.

⁠Artifacts

The purpose of this process is to build code from manageiq-core, manageiq-gemset, and manageiq-appliance into 2 sets of artifacts:

• /root/BUILD/rpm_spec/*.tar.gz
• /root/BUILD/rpms/x86_64/manageiq-*.rpm

One approach is to build and mount a volume that will receive all artifacts:

docker run --rm -v `pwd`/OPTIONS:/root/OPTIONS -v `pwd`/BUILD:/root/BUILD manageiq/rpm_build:latest build

Another approach is to build and copy out the desired artifacts:

CONTAINER='my-build-container'
docker run --name ${CONTAINER} -v `pwd`/OPTIONS:/root/OPTIONS manageiq/rpm_build:latest build
docker cp ${CONTAINER}:/root/BUILD/rpms/x86_64/ ./rpms/
docker rm ${CONTAINER}

⁠Versioning

Branch morphy == v13

⁠License

This code is available as open source under the terms of the Apache License 2.0⁠.