Commit 217f7f05 authored by Jérome Perrin's avatar Jérome Perrin

slapos-testing: don't pin tested eggs

We want the tests to use the code from the repository, but when we have a
pinned version, buildout will use the code from repository only when the
version from the repository match the version spec from the pin.

The way slapos.recipe.template was pinned to 4.4 caused issues when we made
a change in slapos.recipe.template to make it 4.5, because tests were no
longer using code from slapos.recipe.template repository, but from 4.4 egg
from pypi.

To prevent this kind of issues, unset the slapos.recipe.template = 4.4
version pin and also unset the version for all tested egg, to prevent
similar issues if extended profiles also have version pins.
parent 38282357
......@@ -203,14 +203,23 @@ output = ${buildout:directory}/template.cfg
mode = 640
[versions]
# clear version pins of tested eggs for which we want to generate scripts
# otherwise, the scripts will be generated for the pinned version.
slapos.core =
# clear version pins of tested eggs, to make sure buildout always use the
# git checkout version.
caucase =
erp5.util =
kedifa =
slapos.cookbook =
slapos.core =
slapos.libnetworkcache =
slapos.rebootstrap =
slapos.recipe.build =
slapos.recipe.cmmi =
slapos.recipe.template =
slapos.toolbox =
rubygemsrecipe =
# All depencies should be pinned.
Pygments = 2.1.3
slapos.recipe.template = 4.4
zc.lockfile = 1.4
bcrypt = 3.1.4
dnspython = 1.15.0
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment