Apoorva Manjunath
Apoorva Manjunath
For Docker images whose entrypoint is defined and are run as an executable, Dunner fails to execute commands defined in it. Example: [Goreleaser's docker](https://github.com/goreleaser/goreleaser/blob/master/Dockerfile) file. Dunner task file: ``` tasks:...
Currently if the image is private on docker hub and requires login, dunner fails with error message as: ``` docker: checking existence of the image 'ngnix:1.17.3' Pulling image: 'ngnix:1.17.3'... -DEBU[2019-08-26...
Related: https://github.com/leopardslab/dunner/pull/165
Fixes #175
With latest `master`, try : ``` commands: - ["echo","$FOO_USER"] - ["echo", "$BUILD_DIR"] envs: - FOO_USER=foo - BUILD_DIR=`$GOPATH` ``` Environment variables are not passed to container. The commands above do not...
With this feature, user can see scenario level execution in IntelliJ test runner, which adds better UI.
Currently if there is any .md file in a non-gauge project, the gauge intellij plugin treats it as gauge file. But this is not expected.
The sample Gauge projects created by specs are not cleaned up post execution. The hook registered to delete sample project directory is not working and creates memory issues.