You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using Gitlab CI/CD to help build containers, and one of these containers is made up of a number of small shell scripts that I'm validating with Shellspec. I am overriding the default entrypoint and calling the following command:
shellspec -s /bin/bash -o junit
To create junit reports, but as soon as I enable the means to build cobertura reports via kcov by adding "--kcov" to the command, my artifacts for cobertura break the pipeline:
shellspec -s /bin/bash -o junit --kcov
I've determined the issue appears to be with the way the folders are created within the coverage folder, such that it looks like this:
coverage/<project_name> [specfiles]/cobertura.xml
Where <project_name> is the name of the git project, here is a picture of an example of what the directory structure looks like, I've had to black out the project name however:
I'm unsure why the " [specfiles]" is being added to the path, but as soon as I remove that portion from the file name, the pipeline works as expected.
The text was updated successfully, but these errors were encountered:
I am using Gitlab CI/CD to help build containers, and one of these containers is made up of a number of small shell scripts that I'm validating with Shellspec. I am overriding the default entrypoint and calling the following command:
shellspec -s /bin/bash -o junit
To create junit reports, but as soon as I enable the means to build cobertura reports via kcov by adding "--kcov" to the command, my artifacts for cobertura break the pipeline:
shellspec -s /bin/bash -o junit --kcov
I've determined the issue appears to be with the way the folders are created within the coverage folder, such that it looks like this:
coverage/<project_name> [specfiles]/cobertura.xml
Where <project_name> is the name of the git project, here is a picture of an example of what the directory structure looks like, I've had to black out the project name however:
I'm unsure why the " [specfiles]" is being added to the path, but as soon as I remove that portion from the file name, the pipeline works as expected.
The text was updated successfully, but these errors were encountered: