IssueTracker

This is a feature not yet available to the Cloud Build. This feature is currently being worked on by the product team as reported here[1].

The current workaround would be to also mirror the submodule repositories into Cloud Source Repositories separately from the main GitHub repository.
- If relative URLs are used in .gitmodules file, they will automatically be resolved relative to the parent project. This avoids needing to rewrite anything.
- If absolute URLs are used, the builder could use url.insteadOf in ~/.gitconfig to remap URL associations. Or preconfigure entries in the parent project's .git/config using submodule.NAME.url (by cloning the parent without --recursive), and then running 'git submodule update'.

I hope this is workaround is helpful. There is currently no available ETA for the feature implementation as of yet.

[1] https://github.com/GoogleCloudPlatform/cloud-builders/issues/26

I am having this same issue, and was redirected here from [1],

however the workaround mentioned here does not work, as the build asset sent to CloudBuild from the Github CI App on github is not a repository.. unless I am missing something, this is the output of my test repo build with submodule [2]:

=============================================================================
starting build "fa2c589c-ddee-4ebf-8e8a-5d9579fb89b1"

FETCHSOURCE
Fetching storage object: gs://386546555491.cloudbuild-source.googleusercontent.com/4a43eaadc97fd69b3913448be84f3a37a406aaf4-75159a83-fa1b-465c-9769-816e1e707c5d.tar.gz#1566253426161903
Copying gs://386546555491.cloudbuild-source.googleusercontent.com/4a43eaadc97fd69b3913448be84f3a37a406aaf4-75159a83-fa1b-465c-9769-816e1e707c5d.tar.gz#1566253426161903...
/ [0 files][ 0.0 B/ 559.0 B]
/ [1 files][ 559.0 B/ 559.0 B]
Operation completed over 1 objects/559.0 B.
BUILD
Starting Step #0
Step #0: Already have image (with digest): gcr.io/cloud-builders/git
Step #0: /workspace:
Step #0: total 24
Step #0: drwxr-xr-x 3 root root 4096 Aug 19 22:24 .
Step #0: drwxr-xr-x 1 root root 4096 Aug 19 22:24 ..
Step #0: -rw-rw-r-- 1 root root 0 Aug 19 22:23 .gcloudignore
Step #0: -rw-rw-r-- 1 root root 110 Aug 19 22:23 .gitmodules
Step #0: -rw-rw-r-- 1 root root 58 Aug 19 22:23 README.md
Step #0: -rw-rw-r-- 1 root root 283 Aug 19 22:23 cloudbuild.yaml
Step #0: drwxrwxr-x 3 root root 4096 Aug 19 22:23 submodules
Step #0:
Step #0: /workspace/submodules:
Step #0: total 12
Step #0: drwxrwxr-x 3 root root 4096 Aug 19 22:23 .
Step #0: drwxr-xr-x 3 root root 4096 Aug 19 22:24 ..
Step #0: drwxrwxr-x 2 root root 4096 Aug 19 22:23 test-module
Step #0:
Step #0: /workspace/submodules/test-module:
Step #0: total 8
Step #0: drwxrwxr-x 2 root root 4096 Aug 19 22:23 .
Step #0: drwxrwxr-x 3 root root 4096 Aug 19 22:23 ..
Finished Step #0
Starting Step #1
Step #1: Already have image (with digest): gcr.io/cloud-builders/git
Step #1: cat: /workspace/submodules/test-module/README.md: No such file or directory
Finished Step #1
ERROR
ERROR: build step 1 "gcr.io/cloud-builders/git" failed: exit status 1
==================================================================================

as you can see from the build output, the step that runs the `ls -la -R /workspace` does not list any git repository..  So I have no idea how the workarounds could possibly work, as I constantly just get:
Step #2: Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Step #2: fatal: not a git repository (or any parent up to mount point /)

Whenever I attempt to use any `git` command in the cloudbuild spec.

Is there any actual workaround for this currently? or is the entire thing just broken for repos with submodules?

[1] https://issuetracker.google.com/issues/139583419
[2] https://github.com/mpb-com/test-cb-public

Just tried the workaround suggested and I don't think it works as of now. Is there a roadmap of getting this integrated normally?

We started the process of migrating from AzurePipelines to CloudBuild. We were very optimistic until we hit this problem.

Any update to this?  I'm running into this same issue now and wondering if there is any progress on the official solution. Thanks!

Poking this as well, the last Google update was roughly  2 years ago. This is a feature I would expect out of the box with Cloud Build.

For what it's worth, I have a temporary workaround that I use in production.

We have an external submodule that is based on another GitHub repository, I set it up to be mirrored with a Cloud Source Repository. Then, in my Cloud Build step:

```
  - id: '⏬️ Clone submodules'
    name: 'gcr.io/cloud-builders/git'
    entrypoint: 'bash'
    env: ['GIT_DISCOVERY_ACROSS_FILESYSTEM=1']
    args:
    - '-c'
    - |
      git init
      git submodule set-url my-gh-org/repo-name https://source.developers.google.com/p/${PROJECT_ID}/r/github_my-gh-org_repo-name
      git submodule init
      git submodule update --init --recursive
      echo "🦄 Submodules pulled."
```

Essentially, we just replace the local reference to Cloud Source Repository and it works just fine. Would be great if Google could provide an official update in the meantime though.

Previous answer doesn't work or missing instructions.

The answer still works and is what we are using on a daily basis.

Agreed. Answer in comment #10 does not work out of the box. Likely requires other steps/instructions, eg other build steps or non-default setup in files like .gcloudignore.

3rd party repo contains cloudbuild.yaml and no any workaround helps

Hi, why is this not on the roadmap? It is a key feature.

Thanks

The workaround in comment #10 actually works for us. Thanks!

when using event trigger ,   cloud build yaml is from submodule, it doesn't work. we really need it.