Closed orviz closed 3 years ago
@orviz This is wrong and not expected... Tox configuration or any other build tool configuration only appears in the stage where it will run.
@orviz tox.ini file when set should be the full path to the expected location inside container. In PR I was setting the full project path but that is wrong, because the tox will run inside container, so depends on the user configuration for the container itself. So always require the user or the auto-configuration system to set it as expected.
Closing this issue, since is not a bug from JePL side.
Even though the command
tox
itself does not require a configuration file to be provided, JePL is currently requesting that. The erroreu.indigo.compose.DockerCompose.escapeWhitespace(DockerCompose.groovy:117)
is obtained when notox_file
is provided (see sample failure)