Thanks for the link to that issue. But it is not really the issue I am having.
I am not using the CMake build step, but only using it to get the tool in the
path and get auto installers.
Same for the custom tools. Both custom tools and CMake work in the Scripted
Pipeline job type but I can't
It seems that the Declarative Pipeline (Pipeline Model Definition) does not
support some important tools with the "tools" block, in particular the
CMake tool and custom tools.
I tried all combinations I could find of things like
tools {
Those "random number and letter" are Git commit identifiers. They are
SHA-1 hashes of the Git commit object. It's kind of like a Subversion
revision number, except it's more unique. For some reason the "All
Changes" view is showing you the Git commit that each change came from.
On Tuesday,
The workaround of use the 'tool' function in the environment PATH
assignment is working for me.
Here is an example:
pipeline {
agent { label "windows" }
environment {
PATH = """${
[
tool('Ninja'),
[tool('CMake'),
