Re: Cucumber-Gherkin Ruby Browser close

[niristotle okram]

How do you think, someone can possibly help with the below statement?

Please have some common sense while asking for help.

On Thu, Feb 1, 2018 at 12:05 AM Anitha P  wrote:

> When I do a build a Jenkins my browser window atutomatically closes before
> the script . Can some one help me resolve this issue ?
>
> --
> 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/050c6288-2514-4af2-858b-99f864128471%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
Sent from mobile device, excuse typos if any.

-- 
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/CAPzcO4gU27ZZ6hp49Z9kBkhufWNHqNC4oJ%3DLVA-Ch1%2BUKJX14g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Cucumber-Gherkin Ruby Browser close

[Anitha P]

When I do a build a Jenkins my browser window atutomatically closes before 
the script . Can some one help me resolve this issue ?

-- 
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/050c6288-2514-4af2-858b-99f864128471%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: A recent change (or bug) in either Docker and/or Jenkins is breaking most tutorials in the Jenkins User Documentation.

[desmond . lim]

Hi All,

Thanks for everyone's help. I made a big mistake. So it was my problem.

Thank you.

Desmond

On Thursday, February 1, 2018 at 11:18:39 AM UTC+8, desmo...@docdoc.com 
wrote:
>
> Thanks Giles for the update.
>
> Hi All,
>
> I have another issue, I'm doing the deliver (from the tutorial) and I'm 
> getting this error
>
> ./jenkins/scripts/deliver.sh: not found 
> Do I need to put the file in?
>
> Desmond
>
> On Thursday, February 1, 2018 at 6:59:55 AM UTC+8, Giles Gaskell wrote:
>>
>> Hi all and thanks Damien,
>>
>> Just letting everyone know that a new version of the Docker Pipeline 
>> plugin (i.e. version 1.15) was released yesterday (
>> https://plugins.jenkins.io/docker-workflow) and so if you update this 
>> plugin on your Jenkins instances (via Manage Jenkins > Manage Plugins) to 
>> this version (or later), these tutorials will resume running successfully 
>> again.
>>
>> Cheers,
>> Giles.
>>
>> On Tuesday, January 30, 2018 at 9:56:01 PM UTC+11, Damien Duportal wrote:
>>>
>>> Hi,
>>>
>>> you did everything good, it is just that the plugin had not been 
>>> released yet with the fix (it is "merged" on the master branch, but not 
>>> released yet).
>>>
>>> The releases at the "Code" level can be found here: 
>>> https://github.com/jenkinsci/docker-workflow-plugin/releases .
>>> => The last one is 1.1.4.
>>>
>>> On the plugin website, where the plugins you install in Jenkins 
>>> generally come from, it is also at the 1.14 version: 
>>> https://plugins.jenkins.io/docker-workflow .
>>>
>>> With the FOSDEM at the end of the week, I suppose the maintainers are 
>>> busy travelling / sleeping. Let's wait a bit on this.
>>>
>>> Thanks for taking time for putting the feedback together!
>>>
>>> Damien
>>>
>>> On Tue, Jan 30, 2018 at 4:10 AM  wrote:
>>>
 Hi All,

 I've updated all the plug-in for jenkins but I still can't get the 
 tutorial to work. I'm getting this error when it runs

 [simple-java-maven-app] Running shell script
 sh: can't create 
 /var/jenkins_home/workspace/simple-java-maven-app@tmp/durable-3b228035/jenkins-log.txt:
  
 nonexistent directory
 sh: can't create 
 /var/jenkins_home/workspace/simple-java-maven-app@tmp/durable-3b228035/jenkins-result.txt:
  
 nonexistent directory
 script returned exit code -2

 I've even tried reinstall everything, but I'm still getting this error.

 Is it still an issue or am I the only one having this problem

 I'm using a MacBook Pro on High Sierra.

 Thanks.

 On Wednesday, January 24, 2018 at 11:12:58 AM UTC+8, Giles Gaskell 
 wrote:

> Hi everyone,
>
> Just a quick follow-up ...
>
> It's possible that this issue may have resulted from recent changes in 
> Docker behavior (i.e. in recent Docker versions) which were no longer 
> being 
> handled correctly by the Jenkins Docker Pipeline plugin.
>
> Once this PR (
> https://github.com/jenkinsci/docker-workflow-plugin/pull/128) is 
> merged and a new version of this plugin released, then these tutorials 
> should start working again (as documented).
>
> Cheers,
>
 Giles.
>
> On Wednesday, January 24, 2018 at 12:10:09 PM UTC+11, Giles Gaskell 
> wrote:
>
 Thanks so much for all the sleuthing work Damien - you've hit the nail 
>> on the head with this one.
>>
>> Cheers,
>>
> Giles.
>>
>> On 24 January 2018 at 00:43, Damien Duportal  
>> wrote:
>>
> This issue is related to the "Docker Pipeline" plugin 
>>> ("docker-workflow") which has an issue when trying to determine if the 
>>> executor (master or agent) is running inside a container.
>>>
>>> See issue/PR #120 of "docker-workflow-plugin", in particular 
>>> https://github.com/jenkinsci/docker-workflow-plugin/pull/120#issuecomment-357284756
>>>  
>>> which is for the standard "docker".
>>>
>>> Here is my work list items to diagnose this:
>>>
>>> * The tutorials are working quite well with some older version of 
>>> Docker (example: 17.09)
>>> * When the tutorial is not working, wee the build failing, and 
>>> before the error message "shnot found...", we have a difference in 
>>> the 
>>> logs: it says "Jenkins does not seem to be running inside a container".
>>>   - We can also see the "docker run" commands issued by the 
>>> docker-workflow plugin: 
>>> > BEFORE: "--volumes-from "
>>> > AFTER: "-v /var/jenkins_home/:/var/jenkins_home/."
>>> * This log message come from this piece of code on the plugin 
>>> (v.1.14 when writing those lines): 
>>> https://github.com/jenkinsci/docker-workflow-plugin/blob/docker-workflow-1.14/src/main/java/org/jenkinsci/plugins/docker/workflow/WithContainerStep.java#L158-L182
>>> * As Far as I Understand, The function 
>>> 

Re: A recent change (or bug) in either Docker and/or Jenkins is breaking most tutorials in the Jenkins User Documentation.

[desmond . lim]

Thanks Giles for the update.

Hi All,

I have another issue, I'm doing the deliver (from the tutorial) and I'm 
getting this error

./jenkins/scripts/deliver.sh: not found 
Do I need to put the file in?

Desmond

On Thursday, February 1, 2018 at 6:59:55 AM UTC+8, Giles Gaskell wrote:
>
> Hi all and thanks Damien,
>
> Just letting everyone know that a new version of the Docker Pipeline 
> plugin (i.e. version 1.15) was released yesterday (
> https://plugins.jenkins.io/docker-workflow) and so if you update this 
> plugin on your Jenkins instances (via Manage Jenkins > Manage Plugins) to 
> this version (or later), these tutorials will resume running successfully 
> again.
>
> Cheers,
> Giles.
>
> On Tuesday, January 30, 2018 at 9:56:01 PM UTC+11, Damien Duportal wrote:
>>
>> Hi,
>>
>> you did everything good, it is just that the plugin had not been released 
>> yet with the fix (it is "merged" on the master branch, but not released 
>> yet).
>>
>> The releases at the "Code" level can be found here: 
>> https://github.com/jenkinsci/docker-workflow-plugin/releases .
>> => The last one is 1.1.4.
>>
>> On the plugin website, where the plugins you install in Jenkins generally 
>> come from, it is also at the 1.14 version: 
>> https://plugins.jenkins.io/docker-workflow .
>>
>> With the FOSDEM at the end of the week, I suppose the maintainers are 
>> busy travelling / sleeping. Let's wait a bit on this.
>>
>> Thanks for taking time for putting the feedback together!
>>
>> Damien
>>
>> On Tue, Jan 30, 2018 at 4:10 AM  wrote:
>>
>>> Hi All,
>>>
>>> I've updated all the plug-in for jenkins but I still can't get the 
>>> tutorial to work. I'm getting this error when it runs
>>>
>>> [simple-java-maven-app] Running shell script
>>> sh: can't create 
>>> /var/jenkins_home/workspace/simple-java-maven-app@tmp/durable-3b228035/jenkins-log.txt:
>>>  
>>> nonexistent directory
>>> sh: can't create 
>>> /var/jenkins_home/workspace/simple-java-maven-app@tmp/durable-3b228035/jenkins-result.txt:
>>>  
>>> nonexistent directory
>>> script returned exit code -2
>>>
>>> I've even tried reinstall everything, but I'm still getting this error.
>>>
>>> Is it still an issue or am I the only one having this problem
>>>
>>> I'm using a MacBook Pro on High Sierra.
>>>
>>> Thanks.
>>>
>>> On Wednesday, January 24, 2018 at 11:12:58 AM UTC+8, Giles Gaskell wrote:
>>>
 Hi everyone,

 Just a quick follow-up ...

 It's possible that this issue may have resulted from recent changes in 
 Docker behavior (i.e. in recent Docker versions) which were no longer 
 being 
 handled correctly by the Jenkins Docker Pipeline plugin.

 Once this PR (
 https://github.com/jenkinsci/docker-workflow-plugin/pull/128) is 
 merged and a new version of this plugin released, then these tutorials 
 should start working again (as documented).

 Cheers,

>>> Giles.

 On Wednesday, January 24, 2018 at 12:10:09 PM UTC+11, Giles Gaskell 
 wrote:

>>> Thanks so much for all the sleuthing work Damien - you've hit the nail 
> on the head with this one.
>
> Cheers,
>
 Giles.
>
> On 24 January 2018 at 00:43, Damien Duportal  
> wrote:
>
 This issue is related to the "Docker Pipeline" plugin 
>> ("docker-workflow") which has an issue when trying to determine if the 
>> executor (master or agent) is running inside a container.
>>
>> See issue/PR #120 of "docker-workflow-plugin", in particular 
>> https://github.com/jenkinsci/docker-workflow-plugin/pull/120#issuecomment-357284756
>>  
>> which is for the standard "docker".
>>
>> Here is my work list items to diagnose this:
>>
>> * The tutorials are working quite well with some older version of 
>> Docker (example: 17.09)
>> * When the tutorial is not working, wee the build failing, and before 
>> the error message "shnot found...", we have a difference in the 
>> logs: 
>> it says "Jenkins does not seem to be running inside a container".
>>   - We can also see the "docker run" commands issued by the 
>> docker-workflow plugin: 
>> > BEFORE: "--volumes-from "
>> > AFTER: "-v /var/jenkins_home/:/var/jenkins_home/."
>> * This log message come from this piece of code on the plugin (v.1.14 
>> when writing those lines): 
>> https://github.com/jenkinsci/docker-workflow-plugin/blob/docker-workflow-1.14/src/main/java/org/jenkinsci/plugins/docker/workflow/WithContainerStep.java#L158-L182
>> * As Far as I Understand, The function 
>> "getContainerIdIfContainerized()" is returning the Optional.absent() 
>> String 
>> when it is not working, so the condition is false.
>> * This function is implemented here: 
>> 

Re: A recent change (or bug) in either Docker and/or Jenkins is breaking most tutorials in the Jenkins User Documentation.

[Giles Gaskell]

Hi all and thanks Damien,

Just letting everyone know that a new version of the Docker Pipeline plugin 
(i.e. version 1.15) was released yesterday 
(https://plugins.jenkins.io/docker-workflow) and so if you update this 
plugin on your Jenkins instances (via Manage Jenkins > Manage Plugins) to 
this version (or later), these tutorials will resume running successfully 
again.

Cheers,
Giles.

On Tuesday, January 30, 2018 at 9:56:01 PM UTC+11, Damien Duportal wrote:
>
> Hi,
>
> you did everything good, it is just that the plugin had not been released 
> yet with the fix (it is "merged" on the master branch, but not released 
> yet).
>
> The releases at the "Code" level can be found here: 
> https://github.com/jenkinsci/docker-workflow-plugin/releases .
> => The last one is 1.1.4.
>
> On the plugin website, where the plugins you install in Jenkins generally 
> come from, it is also at the 1.14 version: 
> https://plugins.jenkins.io/docker-workflow .
>
> With the FOSDEM at the end of the week, I suppose the maintainers are busy 
> travelling / sleeping. Let's wait a bit on this.
>
> Thanks for taking time for putting the feedback together!
>
> Damien
>
> On Tue, Jan 30, 2018 at 4:10 AM  wrote:
>
>> Hi All,
>>
>> I've updated all the plug-in for jenkins but I still can't get the 
>> tutorial to work. I'm getting this error when it runs
>>
>> [simple-java-maven-app] Running shell script
>> sh: can't create 
>> /var/jenkins_home/workspace/simple-java-maven-app@tmp/durable-3b228035/jenkins-log.txt:
>>  
>> nonexistent directory
>> sh: can't create 
>> /var/jenkins_home/workspace/simple-java-maven-app@tmp/durable-3b228035/jenkins-result.txt:
>>  
>> nonexistent directory
>> script returned exit code -2
>>
>> I've even tried reinstall everything, but I'm still getting this error.
>>
>> Is it still an issue or am I the only one having this problem
>>
>> I'm using a MacBook Pro on High Sierra.
>>
>> Thanks.
>>
>> On Wednesday, January 24, 2018 at 11:12:58 AM UTC+8, Giles Gaskell wrote:
>>
>>> Hi everyone,
>>>
>>> Just a quick follow-up ...
>>>
>>> It's possible that this issue may have resulted from recent changes in 
>>> Docker behavior (i.e. in recent Docker versions) which were no longer being 
>>> handled correctly by the Jenkins Docker Pipeline plugin.
>>>
>>> Once this PR (
>>> https://github.com/jenkinsci/docker-workflow-plugin/pull/128) is merged 
>>> and a new version of this plugin released, then these tutorials should 
>>> start working again (as documented).
>>>
>>> Cheers,
>>>
>> Giles.
>>>
>>> On Wednesday, January 24, 2018 at 12:10:09 PM UTC+11, Giles Gaskell 
>>> wrote:
>>>
>> Thanks so much for all the sleuthing work Damien - you've hit the nail on 
 the head with this one.

 Cheers,

>>> Giles.

 On 24 January 2018 at 00:43, Damien Duportal  
 wrote:

>>> This issue is related to the "Docker Pipeline" plugin 
> ("docker-workflow") which has an issue when trying to determine if the 
> executor (master or agent) is running inside a container.
>
> See issue/PR #120 of "docker-workflow-plugin", in particular 
> https://github.com/jenkinsci/docker-workflow-plugin/pull/120#issuecomment-357284756
>  
> which is for the standard "docker".
>
> Here is my work list items to diagnose this:
>
> * The tutorials are working quite well with some older version of 
> Docker (example: 17.09)
> * When the tutorial is not working, wee the build failing, and before 
> the error message "shnot found...", we have a difference in the logs: 
> it says "Jenkins does not seem to be running inside a container".
>   - We can also see the "docker run" commands issued by the 
> docker-workflow plugin: 
> > BEFORE: "--volumes-from "
> > AFTER: "-v /var/jenkins_home/:/var/jenkins_home/."
> * This log message come from this piece of code on the plugin (v.1.14 
> when writing those lines): 
> https://github.com/jenkinsci/docker-workflow-plugin/blob/docker-workflow-1.14/src/main/java/org/jenkinsci/plugins/docker/workflow/WithContainerStep.java#L158-L182
> * As Far as I Understand, The function 
> "getContainerIdIfContainerized()" is returning the Optional.absent() 
> String 
> when it is not working, so the condition is false.
> * This function is implemented here: 
> https://github.com/jenkinsci/docker-workflow-plugin/blob/docker-workflow-1.14/src/main/java/org/jenkinsci/plugins/docker/workflow/client/DockerClient.java#L311
>  
> * Before diving in the code (and because I really suck at 
> reading/writing code), I first checked my cgroup self file to see what it 
> looks like (smelling Pattern issue...): 
> https://gist.github.com/dduportal/67f965dd935b4fb7d316b798f2a6c2ef
>   - While someone with the tutorial working got this: 
> https://gist.github.com/dduportal/0ac5e5c76043e95fa0b5ff85c1b0c93e
> 

credentials-binding-plugin: Is it intentional that it doesn't expand parameters of type "choice"?

[Ilia Basin]

Hi.
Here's my use case: I have 6 credentials of type "secret file". Their IDs 
are:

project1_integration
project1_acceptance
project1_production

project2_integration
project2_acceptance
project2_production

I also have two projects project1 and project2. I want project1 to have a 
dropdown parameter that would allow to choose one of three secret files and 
project2 to have its own dropdown to choose one of the other three secret 
files.

I tried to create a simple choice parameter with name: CREDS_ID and allowed 
values being the credentials IDs. Then I checked "Use secret text(s) or 
file(s)" and entered the expression ${CREDS_ID} . The build failed with 
"CredentialNotFoundException", just like here: 
https://issues.jenkins-ci.org/browse/JENKINS-31946?focusedCommentId=243381=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-243381

If instead I create a parameter of type "Credentials", the expansion works 
fine. It's strange, because in the end the plugin calls 
findCredentialById() which accepts the string id. With this parameter the 
dropdown contains all 6 credentials. I see no decent way to limit them.

-- 
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/227fba6c-12c0-4914-9250-8462e983ce76%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

How to build a job on multiple platforms/architectures for each commit.

[Jimd]

In a c++ project, when a developer makes a commit I would like to build for 
multiple compilers, operating systems, and x64 + x86. Is there a way to get 
a stacked grid view of all of these pipeline jobs for each commit? 
Something like this?

[image: Image result for bitten ci]

-- 
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/e13d2797-1ef7-4709-b2d1-c39e06e59398%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Get user who cancelled queued jenkins build

[SACHIN V]

Hi All,

Is there a possibility to know the user who cancelled a queued build in 
Jenkins? I would like to get the user id from a groovy script using Jenkins 
API

-- 
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/daeec5d0-41e7-4cfb-a9b8-37cefbf99735%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Where is the CF CLI executable located in a Jenkins server instance?

['Larry Zhang' via Jenkins Users]

HI, i added "cf login... cf push ..." in the "Execute shell" section under 
"Build" in the Jenkins config, and it pushed my code to my cloud 
foundaries. this is good. My question is where is the CF CLI executable 
located? I didn't do need to do configuration to add pcf plugin in the 
configuration, then how this is working? Please explain it? perhaps the 
jenkins instance has the executable installed as a default?

-- 
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/78b93c15-ca6e-46fb-894a-60540dbdf118%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

ConcurrentModificationException in AWS Codebuild plugin

[Vedarth Kulkarni]

Hi,

I am using:

Jenkins: 2.89.3
AWS Codebuild plugin: com.amazonaws:aws-codebuild:0.17 (maven ID)
Pipeline plugin: org.jenkins-ci.plugins.workflow:workflow-aggregator:2.5 
(maven ID)

And I have a multibranch pipeline with Jenkinsfile which looks something 
like this:

pipeline {
agent { label 'master' }

stages {
stage('Checkout') {
steps {
checkout scm
}
}
stage('Test Run') {
failFast true
parallel {
stage('Test Run 1') {
steps {
timestamps {
withCredentials([[$class: 
'AmazonWebServicesCredentialsBinding', credentialsId: 'aws']]) {
awsCodeBuild credentialsId: 'CodeBuild', 
credentialsType: 'jenkins', projectName: 'Proj1', region: 'us-east-1', 
sourceControlType: 'project', sourceVersion: "${env.GIT_COMMIT}"
}
}
}
}
stage('Test Run 2') {
steps {
withCredentials([[$class: 
'AmazonWebServicesCredentialsBinding', credentialsId: 'aws']]) {
awsCodeBuild credentialsId: 'CodeBuild', 
credentialsType: 'jenkins', projectName: 'Proj2', region: 'us-east-1', 
sourceControlType: 'project', sourceVersion: "${env.GIT_COMMIT}"
}
}
}
stage('Test Run 3') {
steps {
withCredentials([[$class: 
'AmazonWebServicesCredentialsBinding', credentialsId: 'aws']]) {
awsCodeBuild credentialsId: 'CodeBuild', 
credentialsType: 'jenkins', projectName: 'Proj3', region: 'us-east-1', 
sourceControlType: 'project', sourceVersion: "${env.GIT_COMMIT}", 
envVariables: "[{VAR, value1}]"
}
}
}
stage('Test Run 4') {
steps {
withCredentials([[$class: 
'AmazonWebServicesCredentialsBinding', credentialsId: 'aws']]) {
awsCodeBuild credentialsId: 'CodeBuild', 
credentialsType: 'jenkins', projectName: 'Proj3', region: 'us-east-1', 
sourceControlType: 'project', sourceVersion: "${env.GIT_COMMIT}", 
envVariables: "[{VAR, value2}]"
}
}
}
stage('Test Run 5') {
steps {
withCredentials([[$class: 
'AmazonWebServicesCredentialsBinding', credentialsId: 'aws']]) {
awsCodeBuild credentialsId: 'CodeBuild', 
credentialsType: 'jenkins', projectName: 'Proj3', region: 'us-east-1', 
sourceControlType: 'project', sourceVersion: "${env.GIT_COMMIT}", 
envVariables: "[{VAR, value3}]"
}
}
}
stage('Test Run 6') {
steps {
withCredentials([[$class: 
'AmazonWebServicesCredentialsBinding', credentialsId: 'aws']]) {
awsCodeBuild credentialsId: 'CodeBuild', 
credentialsType: 'jenkins', projectName: 'Proj3', region: 'us-east-1', 
sourceControlType: 'project', sourceVersion: "${env.GIT_COMMIT}", 
envVariables: "[{VAR, value4}]"
}
}
}
}
}
}
}



in stages `Test Run 3` to `Test Run 6` I am using same Codebuild project 
but with different environment variable values which execute different 
scripts in the build
When I am running the job with above pipeline I am getting following 
exception:

java.util.ConcurrentModificationException
at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:907)
at java.util.ArrayList$Itr.next(ArrayList.java:857)
at 
com.thoughtworks.xstream.converters.collections.CollectionConverter.marshal(CollectionConverter.java:73)
at 
com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69)
at 
com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58)
at 
com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84)
at 
hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265)
at 
hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252)
Caused: java.lang.RuntimeException: Failed to serialize 
CodeBuildAction#logs for class CodeBuildAction
at 
hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256)
at 
hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224)
at 
com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138)
at 

Separating JUnit test reporting for files in different folders

[James Telfer]

Hi,

I suspect the answer to this is no, at least from what I've seen on the 
plugin page and the available options within the Jenkins UI, but worth 
asking.

I've recently migrated a build which used Multijob to Pipline.  The 
Multijob used a number of different build & test jobs, each of which would 
report test results separately.  These jobs aligned to different levels of 
testing (unit/component/system), which were therefore reported separately.  
Under pipeline this doesn't happen, I get all of the results reported 
together under the '(root)' package in the test results view.

Is there any way to get the reporter to report the results from each stage 
separately?

Thanks,
James Telfer

-- 
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/a617b3d5-eedb-4add-8569-3487fae6cff7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Get failing tests related to a maven build in a pipeline script?

[Vincent Massol]

And the solution is simpler, I just need to save the failing tests before 
the maven execution and compare with the full list of failing tests I get 
after that maven execution:
https://github.com/xwiki/xwiki-jenkins-pipeline/commit/1bce23c511fa04a1b26ae012f198c9b99049a100

Thanks
-Vincent

On Wednesday, January 31, 2018 at 7:19:39 AM UTC+1, Vincent Massol wrote:
>
> Actually my code won't work. Just realized that 'env' can only store 
> Strings. Thus I need a way to have some global variable shared between 
> calls to my scripted pipeline library... Any idea?
>
> On Tuesday, January 30, 2018 at 6:15:20 PM UTC+1, Vincent Massol wrote:
>>
>> Thanks Victor. Not sure how failureDiffString would help. The issue is 
>> that this returns the failures from all past maven executions and not just 
>> for the last run.
>>
>> FTM I've done this but it's overly complex and it would be nice to be 
>> able to get the failed tests related only to the last maven execution:
>>
>> https://github.com/xwiki/xwiki-jenkins-pipeline/commit/cd1ed55e12b22f3957ee1a6e099686461886350b
>>
>> Note that I have to go through a global env variable to save the previous 
>> state and compare.
>>
>> Thanks
>> -Vincent
>>
>> On Tuesday, January 30, 2018 at 6:08:13 PM UTC+1, Victor Martinez wrote:
>>>
>>> What about this: 
>>> https://groups.google.com/d/msg/jenkinsci-dev/hI3aSyayYxQ/txGte6HQAAAJ 
>>> ? Not sure whether the failureDiffString method might help you in this case.
>>>
>>> Cheers
>>>
>>

-- 
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/93ea2888-f670-4b8d-9402-44541c4d9702%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Kubernetes-Plugin BadRequest container name must be specified

[Carlos Sanchez]

On Mon, Jan 22, 2018 at 11:27 PM, Chris Denneen  wrote:

> 1. I was using the external name rather than the internal (cluster.local)
> DNS name in the Kubernetes Cloud Configuration in Jenkins
> 2. Even when I switched it appears it's because the port is necessary (
> http://jenkins.jenkins.svc.cluster.local:443) which I found in open issue
> (https://issues.jenkins-ci.org/browse/JENKINS-48368)
>

The port depends on how you expose the jenkins service. You setup the
jenkins service as non ssl in port 443 ? that's wrong


> 3. If Jenkins wasn't running within a Kubernetes cluster but you wanted to
> leverage the slaves/agents to be run on one then I'm guessing a slave
> secret would need to be made available.
>

That depends on how you want to set it up, there are many options and
different authentication providers


>
> Can documentation for #2 and #3 be made/updated for future?
>
> Thanks
>
> On Monday, January 22, 2018 at 3:01:41 PM UTC-5, Chris Denneen wrote:
>>
>> I've installed latest LTS of jenkins and installed latest
>> kubernetes-plugin.
>>
>> I've created 2 pipeline jobs to test:
>>
>> pod-golang from here (https://kumorilabs.com/blog/k
>> 8s-6-integrating-jenkins-kubernetes/)
>> and one from Carlos Sanchez blog here (https://blog.csanchez.org/201
>> 6/10/25/jenkins-kubernetes-plugin-0-9-released/)
>>
>> Both pods create with the following logs and loop:
>>
>> work/capdev-kubernetes » kubectl logs jenkins-slave-1kl4v-flv53
>> Error from server (BadRequest): a container name must be specified for
>> pod jenkins-slave-1kl4v-flv53, choose one of: [golang jnlp]
>>
>> work/capdev-kubernetes » kubectl logs jenkins-slave-pwcwz-2k20s
>> Error from server (BadRequest): a container name must be specified for
>> pod jenkins-slave-pwcwz-2k20s, choose one of: [maven golang jnlp]
>>
>>
>> Is there something else that needs to be done in order to get these to
>> work?
>>
> --
> 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/01214aa2-964c-4819-99e8-75e8c712b9b1%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/CALHFn6NUQPKrVRkcVDducgRAc-f6-r9h7Q2YVJfuGQTKP5J7Dw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Sharing state between pipeline libraries but not between jobs

[Vincent Massol]

Hi guys,

I need to share some global state (Java objects) between 2 pipeline 
libraries.

vars/lib1.groovy:

def call(body)
{
  // set some global state here


  body()
}

vars/lib2.groovy:

def call()
{
  // retrieve the global state here
}

And the Jenkinsfile:

lib1() {
  lib2()
}


Initially I thought about using "env" but it supports only String and I 
need to store a List.

Important: the global state needs to scoped to the job (i.e. another job 
using lib1() and lib2() shouldn't see the state value set).

Any idea?
Thanks a Lot

-- 
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/90dfc783-9f90-420a-b051-c8cb15fb4943%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.