How to test master branch in an automated CI

[ralonsoh]

Hello Peter:

This is more a question than a bug. In OpenStack/Neutron we strongly depend on pyroute2. This is why we want to create a CI job using master branch, instead of the latest released version.

We have followed the manual to install the project from source. However, that works only when a tag version is checked, it doesn't work with master (untagged hash) branch. Do you have a way to do this?

Link: https://review.opendev.org/c/openstack/neutron/+/846288

Thank you in advance.

[svinota]

Yep, that's the task I started to work much more deeply on from my side as well

• one simple package (again, + pyroute2-minimal, but that's not relevant for Neutron)
• static version file ⇒ pip install git+https should work
• some tasks land here: https://github.com/users/svinota/projects/4 you can track it, and please don't hesitate to create tasks for that topic! It's important
• migrated tox ⇒ nox; if you will have — I will accept there any specific Neutron sessions as well; (CI against the master is running on a daily basis on my side, and we can have both sides tests)
• there is already a partly relevant test module: https://github.com/svinota/pyroute2/tree/master/tests/test_linux/test_integration , but
  • there will be more (eventlet)
  • it will migrate to a separate module, so it will not be needed to run all the functional tests to check the Neutron used code

I will elaborate more when I wake up back tonight. And commit some skeleton module.

[svinota]

Started test_neutron integration module, see e70fe89 , more tests on my side will follow.

Added nox session build, see 72ef6f1

Regarding the install —

# 1. using pip
pip install git+https://github.com/svinota/pyroute2.git

# 2. using git, requires nox in the system or in a venv
git clone https://github.com/svinota/pyroute2.git
cd pyroute2
make install

[svinota]

Another possible solution could be publishing nightly builds somewhere, and you could use them to install for the tests.

So tell me which option suits better, and we do this way.

[elajkat]

Thanks, I checked the first option with pip, locally it worked for me, I will check it in Openstack CI:

(pyroute_test) lajoskatona@comp (2022-07-04 09:27:21) ~
$ pip install git+https://github.com/svinota/pyroute2.git
Collecting git+https://github.com/svinota/pyroute2.git
Cloning https://github.com/svinota/pyroute2.git to /tmp/pip-req-build-z_dsncew
Running command git clone -q https://github.com/svinota/pyroute2.git /tmp/pip-req-build-z_dsncew
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing wheel metadata ... done
Building wheels for collected packages: pyroute2
Building wheel for pyroute2 (PEP 517) ... done
Created wheel for pyroute2: filename=pyroute2-0.6.13-py3-none-any.whl size=432266 sha256=56c92fcdc14f1f675342a923281aa2245e3bfa30792b33fd74f3b56b3a25d759
Stored in directory: /tmp/pip-ephem-wheel-cache-3tvp4dx6/wheels/5c/b6/31/ed7725536517164a25b56c7cec283f02b96f8356f84b49872f
Successfully built pyroute2
Installing collected packages: pyroute2
Successfully installed pyroute2-0.6.13
WARNING: You are using pip version 21.0.1; however, version 22.1.2 is available.
You should consider upgrading via the '/home/lajoskatona/pyroute_test/bin/python -m pip install --upgrade pip' command.
(pyroute_test) lajoskatona@comp (2022-07-04 09:27:33) ~
$ pip3 freeze |grep pyr
pyroute2 @ git+https://github.com/svinota/pyroute2.git@60e1a4720b4b0d49e1627eb588a7271817435df4

[svinota]

Yep. The only disadvantage of pip install git+https is that 0.6.13 from there != 0.6.13 from pypi.

But this going to be fixed as well within one week max.

[elajkat]

Thanks for it, for our effort to have quick feedback with master pyroute2 it is good now

[svinota]

Ok, then I close the issue for now.