CodeQL switched to "noble" causing SCons to not function anymore.

[LordOfDragons]

See build failure here: https://github.com/LordOfDragons/denetwork/actions/runs/12642338845/job/35226440472 .
Previous builds ran on "jammy" (like here: https://github.com/LordOfDragons/denetwork/actions/runs/12168781129/job/33940270968). In these builds SCons could be run without a problem. In the upgrade to noble "SCons" got lost and the builds fail.

Request: Add back SCons to the "noble" build image as it has been the case in the "jammy" build image.

[aibaars]

That's unfortunate. As you can see there was a warning at https://github.com/LordOfDragons/denetwork/actions/runs/12168781129/job/33940270968

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see actions/runner-images#10636
--

I'm not sure why scons cannot be found in the new image. Perhaps it was removed. However, even if it isn't present in the image, I would have expected the C++ automatic installation of dependencies feature to automatically install it.

If the scons tool was present by default in the old ubuntu-latest image, then you best file an issue at https://github.com/actions/runner-images asking if it can be put back.

I'll also ask the CodeQL team to look into why scons isn't installed automatically.

[LordOfDragons]

In that case it is the CodeQL dependency installation that is the problem. In the docker images used for regular building jobs (noble, jammy) SCons package is not pre-installed and I have to manually install them. I thought CodeQL uses different docker images since in jammy it just worked.

[aibaars]

It turns out that CodeQL was missing a package index for noble. This should be fixed in the next release which I expect this week or the next.

[LordOfDragons]

Sounds good to me. Can you ping me when it's ready? Then I can give it a test.

[aibaars]

Sounds good to me. Can you ping me when it's ready? Then I can give it a test.

The pre-release can be found here: https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.20.1 . You can use the tools: property of github/codeql-action/init and set it to the URL of a release artifact.

[LordOfDragons]

That repo uses simple mode of CodeQL so I guess I can only test the release version :/