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,
>
> Bumped into the same problem. Tools seems to be very limited with respect 
> to the tools supported. The work around I found is like this:
>     environment {
>         GROOVY_HOME = tool name: 'Groovy-2.4.9', type: 
> 'hudson.plugins.groovy.GroovyInstallation'
>     }
>     stages {
>         stage('Run Groovy') {
>             steps {
>                 bat "${groovy_home}/bin/groovy <script.name>"
>             }
>         }
>     }
>
> I use this for multiple tools we use (cmake, groovy, innosetup.. etc..). 
> The tool name part:
> tool name: 'Groovy-2.4.9', type: 'hudson.plugins.groovy.
> GroovyInstallation'
> Is generated using the snippet generator.
>
> Waiting for the final solution seems to take a lot of time so this works 
> for me right now. 
> Hope it helps.
>
> Frits.
>
>
>
>
>
> On Thursday, February 16, 2017 at 11:56:33 PM UTC+1, Colin Bennett wrote:
>>
>> 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 {
>>          com.cloudbees.jenkins.plugins.customtools.CustomTool "Ninja"
>>          CustomTool "Ninja"
>>          com.cloudbees.jenkins.plugins.customtools.CustomTool("Ninja")
>>          CMake "CMake"
>>          custom "Ninja"
>>          Custom "Ninja"
>>          msys2 "MSYS2"
>>      }
>>
>> Where I have custom tools called "Ninja" and MSYS2, in addition to CMake 
>> tools.
>>
>> Does anyone have an idea how to make Declarative Pipelines work with 
>> custom tools, and CMake?
>>
>> Regards,
>> Colin
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0fa59f64-acf3-4af8-8f52-352f8348b5ad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to