Why does the Windows build generate an swbom, which is simply impossible in some internal network environments?

[Jabbahao]

cpython/PCbuild/regen.targets

Line 100 in 7f2d89a

<Exec Command='$(PythonForBuild) "$(PySourcePath)Tools\build\generate_sbom.py"'/>

Some internal networks cannot access GitHub and cannot perform SBOM operations. As a result, the operations will fail. Is there a build parameter to disable this function?

[StanFromIreland]

Not in most cases, only in the CI, or, if you remove a checksum (currently all packages have one):

cpython/Tools/build/generate_sbom.py

Line 196 in 70d1b08

if "checksums" not in package or "CI" in os.environ:

CC @sethmlarson

[sethmlarson]

Hmm, is there an existing option for "no network"? If so maybe we should respect that option during this stage. Likely what's happening is the CI environment variable is set in this environment (@Jabbahao to confirm)?

[zooba]

is there an existing option for "no network"?

Or just detect the network failure and let things continue? We used to set a variable (something like BuildingForRelease) that would make these kind of optional checks mandatory, to make sure we break our official builds but didn't upset regular users too much. I assume it's still there, not sure if we're setting it anymore though.