Eclipse Editor for jenkinsfile

[panneerrselvam natarajan]

Hi Team,


I am new to Jenkins pipeline and Eclipse, I need to use the eclipse editor 
to create and compile the Jenkins file and finally need to store in Git 
repository.


I have already installed Jenkins editor plugin for Eclipse, Please help me 
to use the editor and compile the pipeline code for error fixing.



Regards

Panneerselvam

-- 
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/33be3e75-b579-4272-a579-2f6b18f72643%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: curl syntax to send and receive REST Service API response (xml) from jenkins

[panneerrselvam natarajan]

Hi Prasad,

Thanks for your response.

I am getting response using HTTP instead of HTTPS and stored in xml file.. 
How do i read the xml file? 
The new XmlParser().parseText() displayed some error

Regards
Panneer



panneerrselvam natarajan wrote:

> Hi All,
>
> I need to execute the test suite using jenkins pipeline, The test suites  
> which has developed using pega (REST service API). Please do let me know 
> syntax to get the xml based response.
>
> Regards
> Panneer
>
>

-- 
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/e1492cbf-f53b-41a5-b854-cdd59825e1b5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Problem with Java 8 update 191?

[James Fairweather]

Today I installed the version of Java from 8 build 181 to 8 build 191 on
several build slaves.  After doing that, Jenkins started allocating a 2nd
workspace on the some of the build agents.  For example, instead of running
here:

D:\projects\lion\main

They were running here:

D:\projects\lion\main@2

Each build agent has been allocated a single executor.  We are running
Jenkins 2.138.2.  I rolled the version of Java on the non-working agents
back to Update 181 and the problem went away.

Does anyone know if Java 8 Update 191 has some kind of incompatibility
problem with Jenkins?

-- 
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/CALg80NUJuzJ8nsMkTqwewuLn4UFvATinP0rvA%3DcMv_n-_WmPfg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found among steps

[Ulli Hafner]

You need to point your update center to the experimental update center url, see 
https://jenkins.io/doc/developer/publishing/releasing-experimental-updates/

Von meinem iPad gesendet

> Am 29.10.2018 um 15:43 schrieb dean warren :
> 
> Thanks @sagar for your reply.
> 
> But the link https://updates.jenkins.io/download/plugins/warnings/ does not 
> contain version 5.0. Perhaps because this is a beta?
> 
> So do I have to build / repackage it, of is there another link that will give 
> me the .hpi file?
> 
>> On Mon, Oct 29, 2018 at 2:22 PM sagar utekar  
>> wrote:
>> from here you can download hpi file for warnings plugin 
>> https://updates.jenkins.io/download/plugins/warnings/
>> 
>> and add it using upload section of manage plugin -> advanced section
>> 
>>> On Mon, Oct 29, 2018 at 7:39 PM def  wrote:
>>> OK, from here:
>>> https://github.com/jenkinsci/warnings-plugin/tree/5.0
>>> 
>>> But Jnekins requires a .hpi file.
>>> Do I have to build this, or package it somehow?
>>> 
 On Monday, 29 October 2018 14:02:45 UTC, def wrote:
 Thanks @ulli for your reply.
 
 'Did you install the 5.0 beta version of the plugin? This step is not 
 available in the 4.x version.'
 Ahh... :) No. Where do I get that from and how to install in Jenkins?
 
> On Sat, Oct 27, 2018 at 6:07 PM Ulli Hafner  
> wrote:
> 
> 
> Von meinem iPad gesendet
> 
>> Am 26.10.2018 um 09:50 schrieb dean warren :
>> 
>> I am trying to get the Warnings plugin collecting CheckStyle results 
>> within a pipeline.
>> I believe I am using all the latest versions of pipeline related 
>> modules, and the warnings modules.
>>  
>> A simplified version of my Jenkinsfile is something like:
>> 
>> timestamps {
>> node ('name') {
>> try
>> {
>> stage ('Checkout') {
>> checkout scm
>> }
>> stage ('Build & Test') {
>> sh 'bash -x test.sh'
>> }
>> stage ('CheckStyle') {
>> sh 'java -jar 
>> /home/user/checkstyle/checkstyle-6.5-all.jar -c 
>> /home/user/checkstyle.xml -f xml -c target/checkstyle-results.xml src'
>> // Doesn't work
>> //step([$class: 'CheckStylePublisher',
>> //canRunOnFailed: true,
>> //defaultEncoding: '',
>> //healthy: '100',
>> //pattern: '**/target/checkstyle-result.xml',
>> //unHealthy: '90',
>> //useStableBuildAsReference: true
>> //])
> 
> This publisher requires the CheckStyle plugin.
> 
>> // Doesn't work
>> //step([$class: 'WarningsPublisher', consoleParsers: 
>> [[parserName: 'CheckStyle']]])
> 
> The warnings publisher from the 4.x version does not support CheckStyle 
> yet.
>  
>> // Doesn't work
>> def checkstyle = scanForIssues tool: [$class: 
>> 'CheckStyle'], pattern: '**/target/checkstyle-result.xml'
>> publishIssues issues:[checkstyle]
>> }
>> }
>> catch (caughtErr)
>> {
>> }
>> finally
>> {
>> }
>> }
>> }
> 
> Did you install the 5.0 beta version of the plugin? This step is not 
> available in the 4.x version.
> 
>> Where I have tried three different methods to collect the checkstype 
>> results, none of which work (I have left two of them commented out for 
>> reference - but beleive these are methods for the legacy checkstyle 
>> plugin, not the newly integrated warnigns plugin?).
>> 
>> I believe the last method using scanForIssues is the correct method as 
>> per here:
>> https://github.com/jenkinsci/warnings-plugin/blob/master/Jenkinsfile.local
>>  
>> However on build, I see the checkstyle results being generated, but get 
>> the following error message
>> java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found 
>> among steps
>> 
>> Any ideas?
>> Thanks in advance!
>> 
>> -- 
>> 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/00750112-2e37-4213-91b3-01c87686433c%40googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the 

Re: java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found among steps

[dean warren]

Thanks @sagar for your reply.

But the link https://updates.jenkins.io/download/plugins/warnings/ does not
contain version 5.0. Perhaps because this is a beta?

So do I have to build / repackage it, of is there another link that will
give me the .hpi file?

On Mon, Oct 29, 2018 at 2:22 PM sagar utekar 
wrote:

> from here you can download hpi file for warnings plugin
> https://updates.jenkins.io/download/plugins/warnings/
>
> and add it using upload section of manage plugin -> advanced section
>
> On Mon, Oct 29, 2018 at 7:39 PM def  wrote:
>
>> OK, from here:
>> https://github.com/jenkinsci/warnings-plugin/tree/5.0
>>
>> But Jnekins requires a .*hpi* file.
>> Do I have to build this, or package it somehow?
>>
>> On Monday, 29 October 2018 14:02:45 UTC, def wrote:
>>
>>> Thanks @ulli for your reply.
>>>
>>> *'Did you install the 5.0 beta version of the plugin? This step is not
>>> available in the 4.x version.*'
>>> Ahh... :) No. Where do I get that from and how to install in Jenkins?
>>>
>>> On Sat, Oct 27, 2018 at 6:07 PM Ulli Hafner 
>>> wrote:
>>>


 Von meinem iPad gesendet

 Am 26.10.2018 um 09:50 schrieb dean warren :

 I am trying to get the Warnings plugin collecting CheckStyle results
 within a pipeline.

 I believe I am using all the latest versions of pipeline related
 modules, and the warnings modules.



 A simplified version of my Jenkinsfile is something like:

 timestamps {
 node ('name') {
 try
 {
 stage ('Checkout') {
 checkout scm
 }
 stage ('Build & Test') {
 sh 'bash -x test.sh'
 }
 stage ('CheckStyle') {
 sh 'java -jar
 /home/user/checkstyle/checkstyle-6.5-all.jar -c /home/user/checkstyle.xml
 -f xml -c target/checkstyle-results.xml src'
 // Doesn't work
 //step([$class: 'CheckStylePublisher',
 //canRunOnFailed: true,
 //defaultEncoding: '',
 //healthy: '100',
 //pattern: '**/target/checkstyle-result.xml',
 //unHealthy: '90',
 //useStableBuildAsReference: true
 //])


 This publisher requires the CheckStyle plugin.

 // Doesn't work
 //step([$class: 'WarningsPublisher',
 consoleParsers: [[parserName: 'CheckStyle']]])



 The warnings publisher from the 4.x version does not support CheckStyle
 yet.


 // Doesn't work
 def checkstyle = scanForIssues tool: [$class:
 'CheckStyle'], pattern: '**/target/checkstyle-result.xml'
 publishIssues issues:[checkstyle]
 }
 }
 catch (caughtErr)
 {
 }
 finally
 {
 }
 }
 }


 Did you install the 5.0 beta version of the plugin? This step is not
 available in the 4.x version.

 Where I have tried three different methods to collect the checkstype
 results, none of which work (I have left two of them commented out for
 reference - but beleive these are methods for the legacy checkstyle plugin,
 not the newly integrated warnigns plugin?).


 I believe the last method using scanForIssues is the correct method as
 per here:


 https://github.com/jenkinsci/warnings-plugin/blob/master/Jenkinsfile.local



 However on build, I see the checkstyle results being generated, but get
 the following error message
 java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found
 among steps

 Any ideas?
 Thanks in advance!


 --
 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/00750112-2e37-4213-91b3-01c87686433c%40googlegroups.com
 
 .
 For more options, visit https://groups.google.com/d/optout.

 --
 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
 

Re: java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found among steps

[sagar utekar]

from here you can download hpi file for warnings plugin
https://updates.jenkins.io/download/plugins/warnings/

and add it using upload section of manage plugin -> advanced section

On Mon, Oct 29, 2018 at 7:39 PM def  wrote:

> OK, from here:
> https://github.com/jenkinsci/warnings-plugin/tree/5.0
>
> But Jnekins requires a .*hpi* file.
> Do I have to build this, or package it somehow?
>
> On Monday, 29 October 2018 14:02:45 UTC, def wrote:
>
>> Thanks @ulli for your reply.
>>
>> *'Did you install the 5.0 beta version of the plugin? This step is not
>> available in the 4.x version.*'
>> Ahh... :) No. Where do I get that from and how to install in Jenkins?
>>
>> On Sat, Oct 27, 2018 at 6:07 PM Ulli Hafner 
>> wrote:
>>
>>>
>>>
>>> Von meinem iPad gesendet
>>>
>>> Am 26.10.2018 um 09:50 schrieb dean warren :
>>>
>>> I am trying to get the Warnings plugin collecting CheckStyle results
>>> within a pipeline.
>>>
>>> I believe I am using all the latest versions of pipeline related
>>> modules, and the warnings modules.
>>>
>>>
>>>
>>> A simplified version of my Jenkinsfile is something like:
>>>
>>> timestamps {
>>> node ('name') {
>>> try
>>> {
>>> stage ('Checkout') {
>>> checkout scm
>>> }
>>> stage ('Build & Test') {
>>> sh 'bash -x test.sh'
>>> }
>>> stage ('CheckStyle') {
>>> sh 'java -jar
>>> /home/user/checkstyle/checkstyle-6.5-all.jar -c /home/user/checkstyle.xml
>>> -f xml -c target/checkstyle-results.xml src'
>>> // Doesn't work
>>> //step([$class: 'CheckStylePublisher',
>>> //canRunOnFailed: true,
>>> //defaultEncoding: '',
>>> //healthy: '100',
>>> //pattern: '**/target/checkstyle-result.xml',
>>> //unHealthy: '90',
>>> //useStableBuildAsReference: true
>>> //])
>>>
>>>
>>> This publisher requires the CheckStyle plugin.
>>>
>>> // Doesn't work
>>> //step([$class: 'WarningsPublisher', consoleParsers:
>>> [[parserName: 'CheckStyle']]])
>>>
>>>
>>>
>>> The warnings publisher from the 4.x version does not support CheckStyle
>>> yet.
>>>
>>>
>>> // Doesn't work
>>> def checkstyle = scanForIssues tool: [$class:
>>> 'CheckStyle'], pattern: '**/target/checkstyle-result.xml'
>>> publishIssues issues:[checkstyle]
>>> }
>>> }
>>> catch (caughtErr)
>>> {
>>> }
>>> finally
>>> {
>>> }
>>> }
>>> }
>>>
>>>
>>> Did you install the 5.0 beta version of the plugin? This step is not
>>> available in the 4.x version.
>>>
>>> Where I have tried three different methods to collect the checkstype
>>> results, none of which work (I have left two of them commented out for
>>> reference - but beleive these are methods for the legacy checkstyle plugin,
>>> not the newly integrated warnigns plugin?).
>>>
>>>
>>> I believe the last method using scanForIssues is the correct method as
>>> per here:
>>>
>>>
>>> https://github.com/jenkinsci/warnings-plugin/blob/master/Jenkinsfile.local
>>>
>>>
>>>
>>> However on build, I see the checkstyle results being generated, but get
>>> the following error message
>>> java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found
>>> among steps
>>>
>>> Any ideas?
>>> Thanks in advance!
>>>
>>>
>>> --
>>> 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/00750112-2e37-4213-91b3-01c87686433c%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>> --
>>> 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/71651BEB-5A46-4E4C-B8E5-C8C688B3D162%40gmail.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> 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 

Re: java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found among steps

[def]

OK, from here:
https://github.com/jenkinsci/warnings-plugin/tree/5.0

But Jnekins requires a .*hpi* file.
Do I have to build this, or package it somehow?

On Monday, 29 October 2018 14:02:45 UTC, def wrote:

> Thanks @ulli for your reply.
>
> *'Did you install the 5.0 beta version of the plugin? This step is not 
> available in the 4.x version.*'
> Ahh... :) No. Where do I get that from and how to install in Jenkins?
>
> On Sat, Oct 27, 2018 at 6:07 PM Ulli Hafner  
> wrote:
>
>>
>>
>> Von meinem iPad gesendet
>>
>> Am 26.10.2018 um 09:50 schrieb dean warren :
>>
>> I am trying to get the Warnings plugin collecting CheckStyle results 
>> within a pipeline.
>>
>> I believe I am using all the latest versions of pipeline related modules, 
>> and the warnings modules.
>>
>>  
>>
>> A simplified version of my Jenkinsfile is something like:
>>
>> timestamps {
>> node ('name') {
>> try
>> {
>> stage ('Checkout') {
>> checkout scm
>> }
>> stage ('Build & Test') {
>> sh 'bash -x test.sh'
>> }
>> stage ('CheckStyle') {
>> sh 'java -jar 
>> /home/user/checkstyle/checkstyle-6.5-all.jar -c /home/user/checkstyle.xml 
>> -f xml -c target/checkstyle-results.xml src'
>> // Doesn't work
>> //step([$class: 'CheckStylePublisher',
>> //canRunOnFailed: true,
>> //defaultEncoding: '',
>> //healthy: '100',
>> //pattern: '**/target/checkstyle-result.xml',
>> //unHealthy: '90',
>> //useStableBuildAsReference: true
>> //])
>>
>>
>> This publisher requires the CheckStyle plugin.
>>
>> // Doesn't work
>> //step([$class: 'WarningsPublisher', consoleParsers: 
>> [[parserName: 'CheckStyle']]])
>> 
>>
>>
>> The warnings publisher from the 4.x version does not support CheckStyle 
>> yet.
>>  
>>
>> // Doesn't work
>> def checkstyle = scanForIssues tool: [$class: 
>> 'CheckStyle'], pattern: '**/target/checkstyle-result.xml'
>> publishIssues issues:[checkstyle]
>> }
>> }
>> catch (caughtErr)
>> {
>> }
>> finally
>> {
>> }
>> }
>> }
>>
>>
>> Did you install the 5.0 beta version of the plugin? This step is not 
>> available in the 4.x version.
>>
>> Where I have tried three different methods to collect the checkstype 
>> results, none of which work (I have left two of them commented out for 
>> reference - but beleive these are methods for the legacy checkstyle plugin, 
>> not the newly integrated warnigns plugin?).
>>
>>
>> I believe the last method using scanForIssues is the correct method as 
>> per here:
>>
>> https://github.com/jenkinsci/warnings-plugin/blob/master/Jenkinsfile.local
>>
>>  
>>
>> However on build, I see the checkstyle results being generated, but get 
>> the following error message
>> java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found 
>> among steps
>>
>> Any ideas?
>> Thanks in advance!
>>
>>
>> -- 
>> 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/00750112-2e37-4213-91b3-01c87686433c%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>> -- 
>> 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/71651BEB-5A46-4E4C-B8E5-C8C688B3D162%40gmail.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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/1d291cec-9b90-44bb-9a82-cd47b0db906b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found among steps

[dean warren]

Thanks @ulli for your reply.

*'Did you install the 5.0 beta version of the plugin? This step is not
available in the 4.x version.*'
Ahh... :) No. Where do I get that from and how to install in Jenkins?

On Sat, Oct 27, 2018 at 6:07 PM Ulli Hafner 
wrote:

>
>
> Von meinem iPad gesendet
>
> Am 26.10.2018 um 09:50 schrieb dean warren :
>
> I am trying to get the Warnings plugin collecting CheckStyle results
> within a pipeline.
>
> I believe I am using all the latest versions of pipeline related modules,
> and the warnings modules.
>
>
>
> A simplified version of my Jenkinsfile is something like:
>
> timestamps {
> node ('name') {
> try
> {
> stage ('Checkout') {
> checkout scm
> }
> stage ('Build & Test') {
> sh 'bash -x test.sh'
> }
> stage ('CheckStyle') {
> sh 'java -jar
> /home/user/checkstyle/checkstyle-6.5-all.jar -c /home/user/checkstyle.xml
> -f xml -c target/checkstyle-results.xml src'
> // Doesn't work
> //step([$class: 'CheckStylePublisher',
> //canRunOnFailed: true,
> //defaultEncoding: '',
> //healthy: '100',
> //pattern: '**/target/checkstyle-result.xml',
> //unHealthy: '90',
> //useStableBuildAsReference: true
> //])
>
>
> This publisher requires the CheckStyle plugin.
>
> // Doesn't work
> //step([$class: 'WarningsPublisher', consoleParsers:
> [[parserName: 'CheckStyle']]])
>
>
>
> The warnings publisher from the 4.x version does not support CheckStyle
> yet.
>
>
> // Doesn't work
> def checkstyle = scanForIssues tool: [$class:
> 'CheckStyle'], pattern: '**/target/checkstyle-result.xml'
> publishIssues issues:[checkstyle]
> }
> }
> catch (caughtErr)
> {
> }
> finally
> {
> }
> }
> }
>
>
> Did you install the 5.0 beta version of the plugin? This step is not
> available in the 4.x version.
>
> Where I have tried three different methods to collect the checkstype
> results, none of which work (I have left two of them commented out for
> reference - but beleive these are methods for the legacy checkstyle plugin,
> not the newly integrated warnigns plugin?).
>
>
> I believe the last method using scanForIssues is the correct method as per
> here:
>
> https://github.com/jenkinsci/warnings-plugin/blob/master/Jenkinsfile.local
>
>
>
> However on build, I see the checkstyle results being generated, but get
> the following error message
> java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found
> among steps
>
> Any ideas?
> Thanks in advance!
>
>
> --
> 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/00750112-2e37-4213-91b3-01c87686433c%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> 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/71651BEB-5A46-4E4C-B8E5-C8C688B3D162%40gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAKYjVYyXG_JszLpW0mKo%2B4iAKEj76g-wHWejAbxQyE_rUUZwHg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: BitBucket endPoint configuration from script error

[Nicholas Brown]

doh, simple typo. I'm just not very good at reading the error messages.

bitbucketEndpointConfiguration.updateEndpoint(BitbucketServerEndpoint)

should be:

bitbucketEndpointConfiguration.updateEndpoint(endPoint)


On Monday, 29 October 2018 13:00:10 UTC, Nicholas Brown wrote:
>
> I've been trying to configure and Bitbucket Server endpoint using groovy 
> script from the script console.
> I've been following the example given here: 
> https://plugins.jenkins.io/cloudbees-bitbucket-branch-source but using 
> a BitbucketServerEndpoint instead of bitbucketCloudEndpoint. My code is:
>
>
> import jenkins.model.Jenkins
> import com.cloudbees.jenkins.plugins.bitbucket.endpoints.*
>  
> def endPoint = new BitbucketServerEndpoint(
> "Bitbucket Server",
> "{{ bitbucket_url }}",
> true, // manageHooks
> "bitbucket_password_credential"
> )
>  
> Jenkins jenkins = Jenkins.getInstance()
>  
> def bitbucketEndpointConfiguration = jenkins.getDescriptor(
> "com.cloudbees.jenkins.plugins.bitbucket.endpoints.BitbucketEndpointConfiguration"
> )
>  
> bitbucketEndpointConfiguration.updateEndpoint(BitbucketServerEndpoint)
>  
> jenkins.save()
>
> I'm getting the following error that I don't understand:
>
> groovy.lang.MissingMethodException: No signature of method: 
> com.cloudbees.jenkins.plugins.bitbucket.endpoints.BitbucketEndpointConfiguration.updateEndpoint()
>  is applicable for argument types: (java.lang.Class) values: [class 
> com.cloudbees.jenkins.plugins.bitbucket.endpoints.BitbucketServerEndpoint] 
> Possible solutions: 
> updateEndpoint(com.cloudbees.jenkins.plugins.bitbucket.endpoints.AbstractBitbucketEndpoint)
>
> Can anyone suggest what I'm doing wrong, and the correct way to do this?
>
>
> Thanks,
>
> Nick
>
>

-- 
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/1068d150-503c-477c-aaeb-6b52b4303ca6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to build in specify container in freestyle job when using Kubernetes plugin?

[Carlos Sanchez]

you can't, you can only do it with pipeline jobs

On Mon, Oct 29, 2018 at 1:56 PM 徐志远  wrote:

> I set up a Container Template as follows, and want to execute shell in it
>
>
> [image: Untitled picture.png]
>
>
>
> but when I use label "pyenv" in freestyle job and use python, I got error
> message:
>
> + whoami
>
> jenkins
>
> + python -V
>
> python: command not found
>
> + pip install python-jenkins
>
> line 17: pip: command not found
>
>
>
> it seems the script run in "jnlp container", instead of "python
> container".
>
>
>
> I searched a lot and found "container" argument could be defined in
> "pipeline", but how can I specify to build in certain container in
> freestyle job?
>
> --
> 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/253c79b2-bc5a-4b9d-ae51-f079d9fb0d37%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CALHFn6Mw5Ymc3q%3DAS1f1ObLWqjfib9oJdLxMvpposhawV1wxyA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

BitBucket endPoint configuration from script error

[Nicholas Brown]

I've been trying to configure and Bitbucket Server endpoint using groovy 
script from the script console.
I've been following the example given 
here: https://plugins.jenkins.io/cloudbees-bitbucket-branch-source but 
using a BitbucketServerEndpoint instead of bitbucketCloudEndpoint. My code 
is:


import jenkins.model.Jenkins
import com.cloudbees.jenkins.plugins.bitbucket.endpoints.*
 
def endPoint = new BitbucketServerEndpoint(
"Bitbucket Server",
"{{ bitbucket_url }}",
true, // manageHooks
"bitbucket_password_credential"
)
 
Jenkins jenkins = Jenkins.getInstance()
 
def bitbucketEndpointConfiguration = jenkins.getDescriptor(
"com.cloudbees.jenkins.plugins.bitbucket.endpoints.BitbucketEndpointConfiguration"
)
 
bitbucketEndpointConfiguration.updateEndpoint(BitbucketServerEndpoint)
 
jenkins.save()

I'm getting the following error that I don't understand:

groovy.lang.MissingMethodException: No signature of method: 
com.cloudbees.jenkins.plugins.bitbucket.endpoints.BitbucketEndpointConfiguration.updateEndpoint()
 is applicable for argument types: (java.lang.Class) values: [class 
com.cloudbees.jenkins.plugins.bitbucket.endpoints.BitbucketServerEndpoint] 
Possible solutions: 
updateEndpoint(com.cloudbees.jenkins.plugins.bitbucket.endpoints.AbstractBitbucketEndpoint)

Can anyone suggest what I'm doing wrong, and the correct way to do this?


Thanks,

Nick

-- 
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/c34251c7-4fdd-40fc-9f33-74709230e95f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Connecting Jenkins to GitHub

[HB]

Thank you.  After installing the GitHub integration plugin and watching the 
video, I was able to create a project just as in the video.

My GitHub repository contains only the README.md file as well, however the 
difference is that my repo is private.  The item I create to my private 
repo on GitHub is not requiring that I add any credentials.  Despite not 
creating any credentials after clicking the git radio button under 'Source 
Code Management', I can just save the item successfully.  I can also click 
on the GitHub link within the project and it takes me right to the repo in 
GitHub.

Does this sound correct?  I feel like it should require defining 
credentials to successfully connect to GitHub.  Or is it that I am being 
successfully connected via the public key that I put in place on the GitHub 
side?  Or is it possibly a cookie that is allowing the connection?  Is that 
something I can verify some how?

Thanks,

HB

On Sunday, October 28, 2018 at 8:32:54 PM UTC-7, sagar utekar wrote:
>
> Hi,
>
> Search for a GitHub integration plugin.
>
> Here is a YouTube video link you can refer - 
> https://youtu.be/Z3S2gMBUkBo
>
> Thank you.
>
> On Mon, 29 Oct 2018, 08:55 HB, > 
> wrote:
>
>> Thank you for the reply.  I am not seeing 'gith' plugin, is that short 
>> for a plugin?  Here are the plugins that I have installed referring to git 
>> and ssh:
>>
>> Git client plugin
>> 2.7.3 
>> Git plugin
>> 3.9.1 
>> GIT server Plugin
>> 1.7 
>> GitHub API Plugin
>> 1.92 
>> GitHub Branch Source Plugin
>> 2.4.1
>> GitHub plugin
>> 1.29.3
>>
>> SSH Credentials Plugin
>> 1.14 
>> SSH Slaves plugin
>> 1.28.1
>>
>> Am I missing plugins that you are referring to?  Thanks again, any 
>> guidance is greatly appreciated..
>>
>> HB
>>
>> On Sunday, October 28, 2018 at 7:07:08 PM UTC-7, Robert Rajendra wrote:
>>>
>>> To integrate Jenkins with github. You need to install gith , github 
>>> plugins with ssh plugin you can read the docs regarding these and get the 
>>> work done
>>>
>>> On Mon, 29 Oct 2018, 3:06 am HB,  wrote:
>>>
 All,

 I am completely new to Jenkins but am tasked with getting a working 
 environment up and running.

 Everything appears to running well as follows:

 RHEL 7.5
 Jenkins ver 2.148

 Installed using the below yum repo:
 [jenkins]
 name=Jenkins
 baseurl=http://pkg.jenkins.io/redhat
 gpgcheck=1

 I have it configured to use Active Directory for user authentication 
 and roles.

 My questions revolve around getting Jenkins connected to GitHub.  I am 
 following these steps:

 https://gist.github.com/misterbrownlee/3708738

 I have created a 'utility user' (say git-jenkins) in GitHub that will 
 ideally be the user that Jenkins uses to connect to GitHub.  I also have 
 created a key pair for the connection.  Since Jenkins runs as user 
 'jenkins' on the server, I created the key pair as this user and imported 
 the public key to the 'git-jenkins' utility user in GitHub.

 I also set:

 Global Config user.name Value
 Global Config user.email Value

 to the 'git-jenkins' GitHub utility user via: Manage Jenkins --> 
 Configure System.


 I am trying to follow these steps:

 - Make sure the Manage Jenkins > Configure System has the right path to 
 git
 - Set the global git user.name and user.email to match your global 
 config options
 - Configure GitHub Web Hook to Manually manage hook urls
 - Click the (?) icon next to the manual option and copy the hook URL 
 you see there
 - Optionally set the service account email as the Jenkins sender email 
 address

 However, I am not able to successfully 'test connection' to GitHub in 
 Manage Jenkins --> Configure System..

 I am able to clone the repository from the command line with a 
 different user than the 'git-jenkins' utility user via Jenkins.  But since 
 the 'jenkins' user on the server does not have a login shell out of the 
 box, I am unable to test from the command line.

 Can anyone point me in the right direction here as to what I might be 
 missing?  I hope I have not confused the situation too much.

 Thanks in advance,

 HB

 -- 
 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-use...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-users/68a52bb7-f242-4cd4-9e53-4792259958fa%40googlegroups.com
  
 
 .
 For more options, visit https://groups.google.com/d/optout.

>>> -- 
>> You received this message 

How to build in specify container in freestyle job when using Kubernetes plugin?

[徐志远]

 

I set up a Container Template as follows, and want to execute shell in it


[image: Untitled picture.png]



but when I use label "pyenv" in freestyle job and use python, I got error 
message:

+ whoami

jenkins

+ python -V

python: command not found

+ pip install python-jenkins

line 17: pip: command not found

 

it seems the script run in "jnlp container", instead of "python container".

 

I searched a lot and found "container" argument could be defined in 
"pipeline", but how can I specify to build in certain container in 
freestyle job?

-- 
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/253c79b2-bc5a-4b9d-ae51-f079d9fb0d37%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How should I configure a Jenkins maven job that will implement the .mvn/extensions.xml?

[Adam Hardy]

Thanks. I run it locally like this: 

mvn clean deploy

Locally mvn can read the pom.yml because it loads the .mvn/extensions.xml 
in the project directory first.

It looks like the Jenkins maven functionality just can't do this, judging 
by your answer recommending the command line approach. 

Is there anything on the horizon to add the functionality? Yaml really 
makes the maven pom so much more readable, I'd hate to ditch it and I'm not 
going to persuade other team members to change their poms over to yaml if 
they can't use the straight-forward Jenkins freestyle or maven job types :(

Regards
Adam

On Thursday, 25 October 2018 00:06:33 UTC+1, Jan Monterrubio wrote:

> How do you run this locally? You should be able to use the same command 
> either through the Pipeline DSL in an ‘sh “command”’ block. 
>
> pipeline {
>
> agent any
>
> stages {
>
> stage('Example') {
>
> steps {
>
> sh 'mvn clean deploy'
>
> }
>
> }
>
> }
>
> }
>
> On Wed, Oct 24, 2018 at 12:48 Adam Hardy  > wrote:
>
>> The simple maven job bombs because it's a yam pom and maven needs the 
>> io.takari.polyglot:polyglot-yaml extension, defined in the 
>> .mvn/extensions.xml in the repo. 
>>
>>

-- 
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/1e7b5704-8dd1-4f11-89f9-a84ea808ebe0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Announce] Gerrit Code Review plugin v0.3.1 is out - supports integration with the Gerrit Trigger Plugin

[Luca Milanesio]

Hi all,
I am pleased to announce that after the Jenkins World 2018 summit in Nice last 
week, the Gerrit Code Review plugin 
(https://wiki.jenkins.io/display/JENKINS/Gerrit+Code+Review+Plugin) has 
received new contributions (thanks Alon) and now support many more use-cases:

Integrates with the Gerrit Trigger Plugin for automating Jenkinsfile simple 
pipelines
Allows posting comments to the source files in Gerrit from a Jenkinsfile 
pipeline step
Fully compliant with the Declarative and Scripting pipelines
Support multiple review labels in a single review step

The release of v0.3.1 is a significant step to bring this new plugin to a whole 
new series of use-cases and opening it to future contributions.

Thanks for everyone involved in reviews, fixes, and contributions. Feel free to 
give it a try and contribute to it.

Luca.

-- 
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/E9B97C53-5077-408F-B8D0-CB84D3DBA896%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: curl syntax to send and receive REST Service API response (xml) from jenkins

[prasad venkata ramasatya Nandagiri]

In the curl command give -o so that you get response back. You can also specify 
output format by using —output-format attribute.

But I prefer http request plugin to make rest calls from pipeline script. It is 
very easy to use. 

https://jenkins.io/doc/pipeline/steps/http_request/

-- 
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/e87a2b82-f400-4872-bb8a-096807126a14%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.