Hello,

Thanks for the reply.

We are using the Interpreted/Scripted Pipeline Jenkins syntax vs the 
Declarative Syntax which does not support steps AFAIK.

Thank You


On Wednesday, August 28, 2019 at 5:48:10 PM UTC-4, Yeikel wrote:
>
> Are you talking about building multiple languages or writing pipeline 
> scripts using other languages?
>
> Building multiple languages/stacks is fine. Just add different steps.
>
> The scripting language supported by Jenkins is groovy which is compatible 
> with Java code.
>
> Other than that, as far as I know all you can do is to generate groovy 
> code from other languages, import and run the generated groovy code. This 
> is really not that convenient so it may not be worth it 
>
> On Wed, Aug 28, 2019, 11:30 AM Dennis Kavanagh <[email protected] 
> <javascript:>> wrote:
>
>> Is that possible....?
>>
>> I am wondering what methods or techniques are available?
>>
>> Is the use of a Declarative or Scripted Jenkinsfile recommended?
>>
>> I understand that separate Jenkinsfiles can be placed in each /src for 
>> each language with Jenkins capable of picking up
>>
>> each found Jenkinsfile and executing the commands included.
>>
>> Thank You
>>
>>
>> -- 
>> 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 [email protected] <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/4b1d74b5-342e-46f8-ac33-06a010432a71%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/4b1d74b5-342e-46f8-ac33-06a010432a71%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/b25cc1ac-22a4-4899-9030-fb64cd295f08%40googlegroups.com.

Reply via email to