No option to pass Git credentials

[epneo-sebastianbaier]

Hi there,

I'm trying to set up a build action with a T3 topology. Therefore "west update" of the action-zephyr-setup needs credentials to checkout other repositories, but there is no way to pass credentials to the "west update" call in action-zephyr-setup.

Is there a way to work around this problem?

Regards Sebastian

[fabiobaltieri]

Hey hi, not sure I fully understand the issue but can you add an extra step to setup git before the action runs?

Something like

      - name: Environment Setup
        run: |
          git config --global user.email "bot@zephyrproject.org"
          git config --global user.name "Zephyr Bot"

Shouldn't be needed unless you are doing a rebase or some other operations though. Feel free to link to an example or a log or something if you can.

[epneo-sebastianbaier]

Hi @fabiobaltieri, that is actually what I meant. However, I solved this a little bit different:

git config --global credential.helper store
echo "https://x-access-token:${{ secrets.PAT }}@github.com" >> ~/.git-credentials

Shouldn't be needed unless you are doing a rebase or some other operations though. Feel free to link to an example or a log or something if you can.

For further explanation, especially because I missed that important information, it is also necessary if private repositories need to be checked out by west init. Or am I missing something?

However, now I have a different issue:

-- west build: generating a build system
Loading Zephyr default modules (Zephyr base).
-- Application: /home/runner/work/repo_name/repo_name/gateway
-- CMake version: 3.29.6
-- Found Python3: /opt/hostedtoolcache/Python/3.11.9/x64/bin/python (found suitable version "3.11.9", minimum required is "3.8") found components: Interpreter
-- Cache files will be written to: /home/runner/.cache/zephyr
-- Zephyr version: 3.7.0-rc2 (/home/runner/work/repo_name/repo_name/zephyr)
-- Found west (found suitable version "1.2.0", minimum required is "0.14.0")
-- Board: esp32s3_devkitc, qualifiers: esp32s3/procpu
-- ZEPHYR_TOOLCHAIN_VARIANT not set, trying to locate Zephyr SDK
-- Found host-tools: zephyr 0.16.8 (/home/runner/work/repo_name/repo_name/zephyr-sdk)
-- Found toolchain: zephyr 0.16.8 (/home/runner/work/repo_name/repo_name/zephyr-sdk)
-- Found Dtc: /home/runner/work/repo_name/repo_name/zephyr-sdk/sysroots/x86_64-pokysdk-linux/usr/bin/dtc (Required is at least version "1.4.6")
-- Found BOARD.dts: /home/runner/work/repo_name/repo_name/zephyr/boards/espressif/esp[32](https://github.com/organisation/repo_name/actions/runs/9855561738/job/27210667040?pr=6#step:9:33)s3_devkitc/esp32s3_devkitc_procpu.dts
-- Generated zephyr.dts: /home/runner/work/repo_name/repo_name/build/zephyr/zephyr.dts
-- Generated devicetree_generated.h: /home/runner/work/repo_name/repo_name/build/zephyr/include/generated/zephyr/devicetree_generated.h
-- Including generated dts.cmake file: /home/runner/work/repo_name/repo_name/build/zephyr/dts.cmake
CMake Error at /home/runner/work/repo_name/repo_name/zephyr/cmake/modules/dts.cmake:383 (message):
  command failed with return code: no such file or directory
Call Stack (most recent call first):
  /home/runner/work/repo_name/repo_name/zephyr/cmake/modules/zephyr_default.cmake:132 (include)
  /home/runner/work/repo_name/repo_name/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
-- Configuring incomplete, errors occurred!
  /home/runner/work/repo_name/repo_name/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  CMakeLists.txt:4 (find_package)

FATAL ERROR: command exited with status 1: /usr/local/bin/cmake -DWEST_PYTHON=/opt/hostedtoolcache/Python/3.11.9/x64/bin/python -B/home/runner/work/repo_name/repo_name/build -GNinja -DBOARD=esp32s3_devkitc/esp32s3/procpu -S/home/runner/work/repo_name/repo_name/app
Error: Process completed with exit code 1.

I changed the actual names of my private repos. It looks strange, that the repo name is used twice /repo_name/repo_name/ during the build. Especially because it is different from what has been configured in the action.yml.

Did you ever tested the action with a T3 topology?

Greetings Sebastian

[epneo-sebastianbaier]

Never mind, the second issue was caused by the GitHub cache of the runner. After deleting it, everything worked.

[fabiobaltieri]

Yeah, I bumped into that issue with renamed repositories as well, something with the sdk script adjusting some path (relocate_sdk.py) and if you rename the repository that path changes but the cached sdk still has the old one, would be tempting to setup the sdk somewhere else but then it may cause some issues if one is using private runners with a setup different than the github one.

Thanks for sharing the snippet for the credential problems, I haven't tested this with private repositories myself and admittedly haven't really tested it with T3 style projects, seems like it works though so good to know.