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
Is your feature request related to a problem? Please describe.
I would like to run gitlab-ci-local from a devcontainer which already has everything needed to build my project and has the same dependencies as the different partial images used in different pipeline jobs.
To avoid adding a level of complexity with the docker executor which is used by default when there is either a job image or a default image, I would like to add the possibility to force the shell executor for the projects that I choose.
Similar topic from #1064 and #1314 but easier to implement.
Describe the solution you'd like I would add an option --shell-executor to the command line which basically always sets imageName to null, I think it should be easy enough to code and should work, and I also hope it works with env conf so that I set it once and for all for each project where I need the option.
I am willing to provide the PR after discussion, once you are ok with the concept.
Describe alternatives you've considered
Loosing execution time and complexity by running the default docker executor
Additional context
From a devcontainer that contains a C++/Bazel or a Java/Maven build system, I want to be able to compile, docker build, deploy locally on minikube in iterations of less than 30s, so each second lost launching a docker is not acceptable.
Thanks for your time,
Regards.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I would like to run gitlab-ci-local from a devcontainer which already has everything needed to build my project and has the same dependencies as the different partial images used in different pipeline jobs.
To avoid adding a level of complexity with the docker executor which is used by default when there is either a job image or a default image, I would like to add the possibility to force the shell executor for the projects that I choose.
Similar topic from #1064 and #1314 but easier to implement.
Describe the solution you'd like
I would add an option --shell-executor to the command line which basically always sets imageName to
null
, I think it should be easy enough to code and should work, and I also hope it works with env conf so that I set it once and for all for each project where I need the option.I am willing to provide the PR after discussion, once you are ok with the concept.
Describe alternatives you've considered
Loosing execution time and complexity by running the default docker executor
Additional context
From a devcontainer that contains a C++/Bazel or a Java/Maven build system, I want to be able to compile, docker build, deploy locally on minikube in iterations of less than 30s, so each second lost launching a docker is not acceptable.
Thanks for your time,
Regards.
The text was updated successfully, but these errors were encountered: