Skip to content

Latest commit

 

History

History
76 lines (51 loc) · 1.81 KB

README.md

File metadata and controls

76 lines (51 loc) · 1.81 KB
Raw

Project

It's used to build tools for PouchContainer. Build package to release is one of examples.

Build package

One important role of this repo is to build deb/rpc package to release PouchContainer.

How to build deb package

First of all, we should build image.

cd ${this-repo}
docker build -f Dockerfile.amd64.ubuntu . -t build-deb-pkg

After that, we run the container to build the package.

docker run -it \ # needs input for password
  -v gpg_keys_dir:/build/keys \ # gpg_keys_dir contains gpg keys.
  -v bundle_dir:/build/bundles \ # bundle_dir contains release files.
  build-deb-pkg ${pouch-commit-id-or-branch-or-tag} ${pkg-version-name}

/build/keys is volume to contains the gpd keys which builder needs. The layout of folder is like:

keys:
  |_ default_key
  |_ public
  |_ private

/build/bundles will contains the release files created by builder. After build, we can retrieve the files from the folder.

In PouchContainer, the ${pkg-version-name} of deb must be like the format:

x.y.z~rc{digit}

Therefore, we can make sure that the policy works right for selecting new version.

How to build rpm package

The usage is the same to deb package.

cd ${this-repo}

docker build -f Dockerfile.amd64.centos . -t build-rpm-pkg

docker run -it \ # needs input for password
  -v gpg_keys_dir:/build/keys \ # gpg_keys_dir contains gpg keys.
  -v bundle_dir:/build/bundles \ # bundle_dir contains release files.
  build-rpm-pkg ${pouch-commit-id-or-branch-or-tag} ${version} ${release}

# release will like 1.el.centos.

NOTE: The gpg_keys_dir doesn't need the default_key file.

In PouchContainer, the ${pkg-version-name} of pkg must be like the format:

x.y.z~rc{digit}

Common scripts

scripts folder will hold any common scripts.