It seems a run-time dependency as your shell script calls it.
My understanding is that test-requirements.txt should mainly include unit tests
requirements.
It is synchronized with OpenStack Pike's global requirements then you should
add the lower bound as well.
Listing upper-constraints doesn’t mean that it will be installed. It only
enforces the right version.
Functest doesn’t leverage on it then why should we force the installation in
our container?
It must be installed as any parser dependency when installing your package.
I can modify your
Hello,
It should have been added as dependency (requirements.txt) in your python
package.
I don’t want to list it in the Dockerfile to bypass your issue.
Cédric
De : opnfv-tech-discuss-boun...@lists.opnfv.org
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] De la part de
that needs to be done?
Attached is a picture. dockerhub doesn't like copy paste.
-Aric
On Wed, Aug 30, 2017 at 7:32 AM, cedric.olliv...@orange.com via RT
<opnfv-helpd...@rt.linuxfoundation.org> wrote:
> Hello,
>
> To be precise, I setup automated builds via Docker to allow testin
Hello,
To be precise, I setup automated builds via Docker to allow testing our Alpine
containers during the development cycle via my public repository.
I think they have been copied (badly partially for settings) for building the
official images (opnfv/functest-xxx) which is not mandatory for
