Currently if --shell-executor-no-image=false is used the runner defaults to docker.io/ruby:3.1.
In case isolation is required, there is no option to run the ci in a custom image.
Added --default-image option.
If set when --shell-executor-no-image=false, the value will be used as a image source for the container.
If not set when --shell-executor-no-image=false, the default docker.io/ruby:3.1 will be used.
If set when --shell-executor-no-image=true (or not set), warring message is displayed.
If set when --shell-isolation, warring message is displayed.
~Fixed typo (or old option name) in arvg.ts:49, from --no-shell-executor-no-image to --shell-executor-no-image~
Included 3 tests to validate proper runner image/shell is used.
Currently if
--shell-executor-no-image=false
is used the runner defaults todocker.io/ruby:3.1
. In case isolation is required, there is no option to run the ci in a custom image.Added --default-image option. If set when
--shell-executor-no-image=false
, the value will be used as a image source for the container. If not set when--shell-executor-no-image=false
, the defaultdocker.io/ruby:3.1
will be used. If set when--shell-executor-no-image=true
(or not set), warring message is displayed. If set when--shell-isolation
, warring message is displayed.~Fixed typo (or old option name) in
arvg.ts:49
, from--no-shell-executor-no-image
to--shell-executor-no-image
~Included 3 tests to validate proper runner image/shell is used.