Repository navigation
Bug: External Needs Ignores Proxy #1103
Description
Currently the Multi Repo Docs build fails behind a proxy server. It looks like the Proxy Settings are ignored. On my system a different port for the Proxy is configured but the build uses the HTTPS standard port:
HTTPSConnectionPool(host='eclipse-score.github.io', port=443)
Download the file via wget works as it connects through the proxy.
The Proxy is set via the Environment Variable HTTP(S)_PROXY
Activity
MaximilianSoerenPollak commentedon May 20, 2025
This should be 'hopefully' resolved by using the MODULE route. We will need a release of score to implement this.
AlexanderLanin commentedon May 20, 2025
If it's fixed easily let's go for it. However, generally we do not support proxy setups in S-CORE. This affects dozens of tools etc.
If this needs to be changed, that would be a new requirement for infrastructure. If this needs to be changed, let's address it in tech lead circle, due to the significant implications (effort).
MaximilianSoerenPollak commentedon May 21, 2025
This solution I mentioned above would basically be something we planned to support anyway. It was the 'bazel module' way of getting the needs.json so the 'release' version.
There could theoretically be a more 'bazel' way to get it via http_file, but I have not had luck getting that to work now, although have not put much time into it.
AlexanderLanin commentedon May 21, 2025
@MaximilianSoerenPollak then we close this ticket as won't fix?
MaximilianSoerenPollak commentedon May 21, 2025
I would leave it open as for now, and if this won't work with the Module approach (which I would be very confused why it wouldn't) then I would close as no-fix as then it would require additional solution that wasn't intended so far.
AlexanderLanin commentedon May 22, 2025
Will be fixed by eclipse-score/docs-as-code#40
MaximilianSoerenPollak commentedon May 23, 2025
This should be fixed today. Will implement the 'module' pathway into process once score has a new release.
MaximilianSoerenPollak commentedon May 26, 2025
This should be fixed/possible now with the release of 'docs-as-code' v0.2.6 and this PR in 'process_description' => eclipse-score/process_description#16
@hoe-jo You can close this, if that indeed solves this issue. Thank you.
AlexanderLanin commentedon May 26, 2025
Discussed in TL round. No proxy support for now. Fallback via Codespaces, locally cloning both repositories, or depending on official releases.
MaximilianSoerenPollak commentedon Jun 5, 2025
@hoe-jo Is this one fixed from your side too? So you now can build the docs via the 'release' approach without issues?
MaximilianSoerenPollak commentedon Jun 6, 2025
Will close this issue for now as it seems fixed.
If it's not fixed for anybody, just re-open it.