Suraj Deshmukh

2 minute read

I generally do kompose package testing for fedora and CentOS. So here are the steps I follow.

Fedora

For respective fedora version use the tag respectively for e.g. 25 for fedora 25.

Starting the environment:

docker run -it registry.fedoraproject.org/fedora:26 bash

Running tests:

# Inside the container
# Pull packages from the testing repository
dnf --enablerepo updates-testing -y install kompose

# Check the kompose version
kompose version

# Install the testing dependencies
dnf install -y jq make

# Pull the git repository to run the functional tests
git clone https://github.com/kubernetes/kompose/
cd kompose
git reset --hard $(kompose version | cut -d "(" -f2 | cut -d ")" -f1)

# Run cmd tests
make test-cmd

CentOS epel repo

Spin the CentOS environment in container.

docker run -it centos bash

Running tests:

# Install kompose from 'epel-testing' repo
yum install -y epel-release
yum --enablerepo=epel-testing -y install kompose

# Install the testing dependencies
yum install -y jq make

# Pull the git repository to run the functional tests
git clone https://github.com/kubernetes/kompose/
cd kompose
git reset --hard $(kompose version | cut -d "(" -f2 | cut -d ")" -f1)

# Run cmd tests
make test-cmd

CentOS paas7-openshift-common-el7 repo

Spin the CentOS environment in container.

docker run -it centos bash

Running tests:

# For pulling package from testing repo in CentOS PAAS sig
yum -y install centos-release-openshift-origin
yum -y --enablerepo=centos-openshift-origin-testing install kompose

# Install the testing dependencies
yum install -y epel-release
yum install -y jq make

# Pull the git repository to run the functional tests
git clone https://github.com/kubernetes/kompose/
cd kompose
git reset --hard $(kompose version | cut -d "(" -f2 | cut -d ")" -f1)

# Run cmd tests
make test-cmd

If all tests pass then just give a karma for it on the release page.

Ref:

comments powered by Disqus