Note - To make what Colin did work, you must be using declarative pipeline
1.2 or higher which has its own list of dependencies. I didn't realize this
right away.
On Monday, October 16, 2017 at 12:03:26 PM UTC-5, Colin Bennett wrote:
>
> The workaround of use the 'tool' function in the
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'),
This did not work for me since the tool type I want is of customtools type:
tool name: 'bzip2', type:
'com.cloudbees.jenkins.plugins.customtools.CustomTool'
Are there any alternatives at this point?
Thanks,
Srujana
On Friday, 6 October 2017 11:38:13 UTC-5, Frits van der Holst wrote:
>
> Hi,
> On 17.02.2017, at 02:57, Colin Bennett wrote:
>
> Same for the custom tools. Both custom tools and CMake work in the Scripted
> Pipeline job type but I can't get it to work in the Declarative Pipeline
> syntax.
I think Andrew mentioned on Wednesday that tools need to have
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
February 16, 2017 at 2:56 PM
To: Jenkins Users <jenkinsci-users@googlegroups.com>
Subject: Declarative pipeline support for tools: CMake, custom tools
It seems that the Declarative Pipeline (Pipeline Model Definition) does not
support some important tools with the "tools" block, in particula
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 {