ibek-support git submodule in Generic IOC not initialised during build #114
-
Just a little feedback to consider - I'm not sure if anything specifically is broken or if I've just done something wrong... This morning, I thought I've broken everything - I got myself wound into a knot trying to update the ibek-support submodule with a couple of very minor changes. I managed to make the relevant change and commit them to both my forked ibek-support repo and generic IOC repo. GH Actions now builds so repos are in a good state. However, my local build was broken - there were issues with my added files from devcontainer belonging to root and things got messed up trying to fix that with chown. But because the repos were now in a building state on github, I decided to wipe my local ioc-ads directory entirely and clone it again. I followed the steps from the "Changing Generic IOC" tutorial. Only now the Running the I'm running bash 5.1.16 on Ubuntu 22.04. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 5 replies
-
(this question is transferred from email thread with @gilesknap this morning...) |
Beta Was this translation helpful? Give feedback.
-
It is not intentional that the folder exists until you init the submodule but maybe an empty one has crept into the template. I'll check that. I do agree that a more robust check is required. I'm updating the template right now and will put that in. Regarding use of docker. We are a podman shop and it works beautifully with devcontainers such that file ownership is never an issue. Nevertheless I do work with docker at home and have the following tips that may not yet be documented.
|
Beta Was this translation helpful? Give feedback.
It is not intentional that the folder exists until you init the submodule but maybe an empty one has crept into the template. I'll check that. I do agree that a more robust check is required. I'm updating the template right now and will put that in.
Regarding use of docker. We are a podman shop and it works beautifully with devcontainers such that file ownership is never an issue. Nevertheless I do work with docker at home and have the following tips that may not yet be documented.