Using a Docker image already containing the target repo's master branch

[130s]

I intend to use a Docker image where the source of the target repo is already cloned in, then it only needs to checkout the pull request's branch.
(I do this in order to save time as the target repo is gigabytes large (using Git LFS etc.) and CI often hits the CI's time limit.)

Currently this doesn't work as the workspace is read-only, so all attempts I've tried to update the target repo failed. I do not have a decisive opinion to an open PR #123

What will be the best way to do with industrial_ci?

[130s]

A little more description for my usecase might be necessary.

A test in the target repo runs a downstream tests, and it requires a specific branch that's also available in a PR to the downstream repo. In other words, a PR to repo-A always comes with a PR to the downstream repo-B. To save the CI exec time, the aforementioned Docker image contains downstream pkgs as well.

I might have been wrong in my 1st post #241 (comment) in that the source of the target repo should be even cloned to inside of Docker without problems. So my real problem might be to update downstream code in the pre-built Docker image during industrial_ci process.

Anyways in a nutshell, how to change the code in the workspace during industrial_ci process?

Hope this makes sense and also I'm not making an XY problem..

[mathias-luedtke]

Anyways in a nutshell, how to change the code in the workspace during industrial_ci process?

rosdep wstool?
If you need to overlay packages, you can even setup workspace chaining.

[mathias-luedtke]

#361 will just overwrite the code