You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ATM efc's west manifest is fetching zephyr repository through HTTPS instead of SSH. This is really impractical when implemention requires changes to eurus fork of zephyr repository. I tried to switch to SSH URLs in west.yml but this brought up issues with CI that needs the SSH keys to even pull the zephyr repo through west.
Possible courses of action:
Create separate manifest file for CI with HTTPS repositories only, and migrate original west.yml to use SSH
Find a way to provide build workflow script with SSH access
The text was updated successfully, but these errors were encountered:
There seems to be an additional layer of this problem as some developers are using HTTPS remotes and others SSH. I guess it would be best to allow both within west manifest somehow, but I'm not sure this is actually possible. This zephyr issue that I've stumbled upon doesn't seem resolved yet.
I've left HTTPS remotes in the west manifest for the time being to pacify CI, but it is quite inconvenient that I had to change git remote manually after doing clean setup.
ATM efc's west manifest is fetching zephyr repository through HTTPS instead of SSH. This is really impractical when implemention requires changes to eurus fork of zephyr repository. I tried to switch to SSH URLs in west.yml but this brought up issues with CI that needs the SSH keys to even pull the zephyr repo through west.
Possible courses of action:
The text was updated successfully, but these errors were encountered: