Using a Custom Tool from a Pipeline (with "tool") kind of works; the tool gets installed, and you get back the path to its homedir. But:
- if the tool declares extra PATH entries (for instance for a "bin" sub-folder), you must know it, and set the PATH+BLAH accordingly in your "withEnv" wrapper arguments
- if the tool declares other extra environment variables, you must know it too, and explicitly define them in your Pipeline, again using "withEnv"
So basically, you must be aware of some internal details of the Custom Tool definition, and replicate them in your Pipeline. (And that's just what I find annoying for my use cases, but I don't use all features of Custom Tools; I've never played with "versions", I don't know how they work in a Pipeline context.) |
