Use tox for testing inside a container #1884

2021-11-17T20:30:47+01:00

g1itch commented

2021-11-17 20:30:47 +01:00

(Migrated from github.com)

Hi!

I'm rewriting the packages/Dockerfile.travis and the corresponding script to test using tox.

Hi! I'm rewriting the `packages/Dockerfile.travis` and the corresponding script to test using tox.

g1itch commented

2021-11-18 20:05:27 +01:00

(Migrated from github.com)

I'm still missing something important: surprisingly this reproduces my old issue with shutdown tests in Fedora container.

PeterSurda commented

2021-12-01 11:59:14 +01:00

(Migrated from github.com)

I decided to unify the docker files (at least within one distro version) and use multi stage build. Maybe you can look at Dockerfile.bionic and create a new stage called "tox" (or "test").

I decided to unify the docker files (at least within one distro version) and use multi stage build. Maybe you can look at `Dockerfile.bionic` and create a new stage called "tox" (or "test").

g1itch commented

2021-12-06 20:29:05 +01:00

(Migrated from github.com)

I decided to unify the docker files (at least within one distro version) and use multi stage build. Maybe you can look at Dockerfile.bionic and create a new stage called "tox" (or "test").

I'm not familiar with the multistage builds. Maybe it's a good Idea. Also I still haven't configured a local buildbot instance to propose some changes in the master.cfg. So I decided to start with this test script. What I wanted to show here is that you can have 3 VMs (or containers): xenial?, bionic, focal and use them for all the checks replacing the CMD by tox, tox -e py27-doc or a script for building a package; then remove all the code related to travis or custom package installation from the master.cfg.

Also I don't like the current state of the Dockerfile.bionic, it contains many unneeded packages and produces 2.5 GB image.

> I decided to unify the docker files (at least within one distro version) and use multi stage build. Maybe you can look at `Dockerfile.bionic` and create a new stage called "tox" (or "test"). I'm not familiar with the multistage builds. Maybe it's a good Idea. Also I still haven't configured a local buildbot instance to propose some changes in the `master.cfg`. So I decided to start with this test script. What I wanted to show here is that you can have 3 VMs (or containers): xenial?, bionic, focal and use them for all the checks replacing the CMD by `tox`, `tox -e py27-doc` or a script for building a package; then remove all the code related to travis or custom package installation from the `master.cfg`. Also I don't like the current state of the `Dockerfile.bionic`, it contains many unneeded packages and produces 2.5 GB image.

This repo is archived. You cannot comment on pull requests.

1 Participants

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Bitmessage/PyBitmessage-2025-02-20#1884