Shell-executor build folder isolation
See original GitHub issueFirst of all thanks for this great tool, it’s awesome 😃
I wish there would be a way to let the pipeline run in another isolated directory so that changes done by the pipeline don’t affect the repository itself.
For example the command could look like this:
gitlab-ci-local --dir build
This would then create a directory called build
, copy the project’s content into it and run the pipeline in that directory.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Advanced configuration - GitLab Docs
Absolute path to a directory where build caches are stored in context of selected executor. For example, locally, Docker, or SSH. If the...
Read more >Building Dotnet with Gitlab CI - dotnetthoughts
A runner is an isolated (virtual) machine that picks up builds through the ... Make sure you have nuget.exe is installed on C:\Nuget...
Read more >Securing GitLab CI pipelines with Sysbox - Nestybox Blog Site
It allows the GitLab CI jobs to use the shell executor or Docker executor (either the DooD or DinD approaches) without compromising host ......
Read more >Introduction to GitLab CI/CD pipelines: a complete guide to get ...
The shell executor has a much lower level of isolation, because it runs ... The example above declared 4 jobs ( build-job, unit-test-job, ......
Read more >How to use GitLab CI to run tests locally? - LambdaTest
Parallel builds: Builds split by GitLab CI/CD are designed for faster ... In the root directory of your repository, you must create a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
That’s what I thought. I think, we would have to recreate what an actual runner does, and that is to create a folder for each job, when they are run simultaneously. That way the tool could simulate artifacts workflows as well. I’ll have a look tonight.
4.9.5 contains job isolation via /build/ folders for docker-executor. Are you using shell-executor in your use-case @MoritzBrueckner