date:20150918

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-29941 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Using Configuration Slicer unsets the "Ignore post-commit hooks" checkbox for polled builds  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Michael Donohue Path: src/main/java/configurationslicing/timer/AbstractTimerSliceSpec.java src/main/java/configurationslicing/timer/SCMTimerSliceStringSlicer.java src/main/java/configurationslicing/timer/TimerSliceStringSlicer.java http://jenkins-ci.org/commit/configurationslicing-plugin/7474a28792b19149354799e5a38652fef9eb8b8a Log: Provide the old trigger object when configuring a new timer trigger 
This allows the slice implementor to copy any values that are not of interest to the given slice. This was motivated by the bug JENKINS-29941, and this commit includes a fix for that bug. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [fitnesse-plugin] (JENKINS-30534) The fitness config get lost with a condition step

2015-09-18 Thread augustin...@hotmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Augustin Chen created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30534 
 
 
 
  The fitness config get lost with a condition step  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Antoine Aumjaud 
 
 
 

Components:
 

 fitnesse-plugin 
 
 
 

Created:
 

 18/Sep/15 6:26 AM 
 
 
 

Environment:
 

 Jenkins 1.620 + Fitness plugin 1.16 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Augustin Chen 
 
 
 
 
 
 
 
 
 
 
I install the fitness plugin 1.16.  I config the fitness builder with condition step, all my fitness config get lost when I save the job. As 

JENKINS-21636
 suggests, this issue has been address in release 1.13, but it seems 1.16 has the same issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [dashboard-view-plugin] (JENKINS-12205) Test result trend not displayed in matrix project configuration top page

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-12205 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Test result trend not displayed in matrix project configuration top page  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Willem Verstraeten Path: src/main/java/hudson/plugins/view/dashboard/test/TestUtil.java src/test/java/hudson/plugins/view/dashboard/test/TestSummaryForMatrixJobs.java src/test/resources/hudson/plugins/view/dashboard/test_failure.xml http://jenkins-ci.org/commit/dashboard-view-plugin/117b3666733afa3a6507f8d59ff6568adfdfd6a8 Log: Merge pull request #34 from willemv/master 
[FIXED JENKINS-12205] : show test statistics for Matrix Jobs 
Compare: https://github.com/jenkinsci/dashboard-view-plugin/compare/09948c53a111...117b3666733a 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [dashboard-view-plugin] (JENKINS-12205) Test result trend not displayed in matrix project configuration top page

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-12205 
 
 
 
  Test result trend not displayed in matrix project configuration top page  
 
 
 
 
 
 
 
 
 

Change By:
 
 SCM/JIRA link daemon 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [dashboard-view-plugin] (JENKINS-12205) Test result trend not displayed in matrix project configuration top page

2015-09-18 Thread stanislav.bashkirt...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-12205 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Test result trend not displayed in matrix project configuration top page  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Willem Verstraeten Path: src/main/java/hudson/plugins/view/dashboard/test/TestUtil.java src/test/java/hudson/plugins/view/dashboard/test/TestSummaryForMatrixJobs.java src/test/resources/hudson/plugins/view/dashboard/test_failure.xml http://jenkins-ci.org/commit/dashboard-view-plugin/dabdd8e91c98081aed3becff729a9ea89944048d Log: [FIXED JENKINS-12205] : recent versions of MatrixProject no longer include the test results of their child jobs. Iterate over them manually. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [saml-plugin] (JENKINS-29086) User IDs are case sensitive in saml-plugin

2015-09-18 Thread 0xc...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikhail Tyuzin commented on  JENKINS-29086 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: User IDs are case sensitive in saml-plugin  
 
 
 
 
 
 
 
 
 
 
Have you tried to apply "make all lowercase" rule on SAML IdP side? Usually this could be done on per-app basis so even in in a big company this should not be a problem. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [saml-plugin] (JENKINS-29086) User IDs are case sensitive in saml-plugin

2015-09-18 Thread bren...@letrabb.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brantone commented on  JENKINS-29086 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: User IDs are case sensitive in saml-plugin  
 
 
 
 
 
 
 
 
 
 
Correct, hence commit message as "work around" ... in my specific scenario where RBS is used (and even has help message of "By default user/group names are case sensitive so it needs to match with your user/group definition under Configure Global Security->Access Control->Security Realm." There's already the requirement for case-sensitivity ... furthermore utilizing an SSO SAML setup where user ids are inconsistent (25% are upper-case and rest are lower-case), having a standard of "everything lower case" at least makes it consistent. (I'm in a large org where I know forcing the upstream system to standardize is pointless). 
I was originally hoping for something "easier" by way of a definition in the "IdP Metadata", but my research proved that as a dead-end since SAML is authoritative ... maybe I'm wrong though. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [warnings-plugin] (JENKINS-30551) Make Warnings Plugin compatible with parallel Workflow

2015-09-18 Thread rol...@utk.edu (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Roland Schulz created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30551 
 
 
 
  Make Warnings Plugin compatible with parallel Workflow  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Ulli Hafner 
 
 
 

Components:
 

 warnings-plugin 
 
 
 

Created:
 

 19/Sep/15 12:53 AM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Roland Schulz 
 
 
 
 
 
 
 
 
 
 
29959 made it compatible with a single build. But it doesn't yet work nicely for multiple parallel builds. 
If one puts the WarningsPublisher inside each parallel task, then the build page contains a link to the warning output once per task. But each link points to the same page and only contains the warnings of one task. 
If instead one runs the WarningsPublisher step only once after all all parallel tasks, then the links to the source code do not work (because the workspace path is different on the different node) and the list of warnings doesn't show for which task/node the warning occurred. 
Based on how other plugins (e.g. junit) work, I assume the first is how it should work. To it work, the warnings plugin should summarize the warnings before reporting them.  
To make the 2nd work it would need to parse the task label in the console output (to display the task) and resolve the workspace relative to the node of that task. 
Is anyone working on this? Any suggestions of how to get started on fixing this?

[JIRA] [core] (JENKINS-14605) Simple means to obtain logged in user's id

2015-09-18 Thread bharat...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 bharat goel commented on  JENKINS-14605 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Simple means to obtain logged in user's id  
 
 
 
 
 
 
 
 
 
 
Hi Stanislav 
I have a similar problem which i am trying to solve to capture log in user name. Please suggest were you able to get this info? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-14605) Simple means to obtain logged in user's id

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 stanislav bashkirtsev commented on  JENKINS-14605 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Simple means to obtain logged in user's id  
 
 
 
 
 
 
 
 
 
 
Was too long ago, don't even remember the fact that I asked this question, sorry  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-29340) E200015: ISVNAuthentication provider did not provide credentials

2015-09-18 Thread rec...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto commented on  JENKINS-29340 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: E200015: ISVNAuthentication provider did not provide credentials  
 
 
 
 
 
 
 
 
 
 
Ralf Mühle 
Please, file a new JIRA ticket including a step by step process to reproduce the bug. 
The bug described in this ticket was resolved and confirmed by users. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [other] (JENKINS-29632) Long text in "Configure" elements do not word wrap

2015-09-18 Thread vijay.bu...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vijay Burgu commented on  JENKINS-29632 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Long text in "Configure"  elements do not word wrap  
 
 
 
 
 
 
 
 
 
 
Hi, 
I am also facing the issue. Could you please suggest a solution here. I want the text to fit to my window instead of expanding to the string length. 
Thanks & Regards, Vijay 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [msbuild-plugin] (JENKINS-30489) msbuild configuration need full path with including msbuild.exe but website shows warning

2015-09-18 Thread ronny.borch...@muehlbauer.de (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ronny Borchert updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30489 
 
 
 
  msbuild configuration need full path with including msbuild.exe but website shows warning  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ronny Borchert 
 
 
 

Summary:
 
 msbuild configuration need full  paht  path  with including msbuild.exe but website shows warning 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [container-slaves-plugin] (JENKINS-30538) Set environment variables in builds container

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nicolas De Loof created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30538 
 
 
 
  Set environment variables in builds container  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Nicolas De Loof 
 
 
 

Components:
 

 container-slaves-plugin 
 
 
 

Created:
 

 18/Sep/15 9:15 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Nicolas De Loof 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to

[JIRA] [container-slaves-plugin] (JENKINS-30539) Update `/etc/group` and `/etc/passwd` to add jenkins:jenkins

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nicolas De Loof created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30539 
 
 
 
  Update `/etc/group` and `/etc/passwd` to add jenkins:jenkins  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Nicolas De Loof 
 
 
 

Components:
 

 container-slaves-plugin 
 
 
 

Created:
 

 18/Sep/15 9:16 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Nicolas De Loof 
 
 
 
 
 
 
 
 
 
 
this would avoid permission issues and missing user in containers we run during the build 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA

[JIRA] [subversion-plugin] (JENKINS-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.

2015-09-18 Thread krah.tm+jenk...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Torsten Krah commented on  JENKINS-22542 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Subversion polling not work with externals or variables in URL - E200015: No credential to try.  
 
 
 
 
 
 
 
 
 
 
If there is an issue there - can you link the upstream bugreport from SVNKit in this ticket please? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-plugin] (JENKINS-30515) scm (git) command does not fail correctly when it cannot look up credentials

2015-09-18 Thread magnus.jacobs...@netinsight.net (JIRA)

Title: Message Title

stephenconnolly commented on JENKINS-30515

Re: scm (git) command does not fail correctly when it cannot look up credentials

So this all gets "fun" really fast.
The first thing is that we need to ensure that we are respecting the build authentication. If somebody uses the Authorize Project plugin (or equivalent) then the build will not be running as ACL.SYSTEM.
So the rule should be:

Look up the credentials as Jenkins.getAuthentication()

If none found and Jenkins.getAuthentication() has CredentialsProvider.USE_ITEM then look up the credentials as ACL.SYSTEM

That's all fine and mostly ok...
Now what happens when the job is configured to be parameterized and the credentials are provided from a parameter?
In that case git's credentialId will be something like "${CREDENTIAL_PARAM}"
When faced with such a credentialId, we need to add the User who triggered the build into the mix... the sequence then becomes (for an id that contains ${ and }:

Resolve the ID in the context of the current build by expanding the token macros

If the user who triggered the build has CredentialsProvider.USE_OWN then search for the resolved ID as the user who triggered the build.

If none found and the user who triggered the build has CredentialsProvider.USE_ITEM then search for the resolved ID as ACL.SYSTEM

If none found then look up the credentials as Jenkins.getAuthentication()

If none found and Jenkins.getAuthentication() has CredentialsProvider.USE_ITEM then look up the credentials as ACL.SYSTEM

The good news is that CredentialsProvider.findCredentialsById(..., Run, ...) does all that logic for you... so as long as you are using that method, the credential lookup should be correct.
OK, so how does that affect whether the build should continue or fail...
The credential parameter can be configured to allow selection of no credentials as a valid option.
Thus the job configuration might anticipate that it is valid to not select credentials (I can think of a job where you do a dry run of the release if no credentials to commit back are provided)...
So I think that if the credentialsId is non-empty and we do not find any

[JIRA] [core] (JENKINS-30039) Regression in queue control in Jenkins 1.607: Build are executed concurrently although "Execute concurrent builds if necessary" is not ticked

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Magnus Jacobsson commented on  JENKINS-30039 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Regression in queue control in Jenkins 1.607: Build are executed concurrently although "Execute concurrent builds if necessary" is not ticked  
 
 
 
 
 
 
 
 
 
 
I've tested the test minimum test case against a number of Jenkins version and have come to the conclusion that it is a regression introduced in Jenkins version 1.607. Here are the results: 
Jenkins 1.606 OK for 13+2 hours Jenkins 1.607 1st error after 20 minutes, 1 error during 1 hour Jenkins 1.608 1st error after 16 minutes, 2 errors during 24 minutes  Jenkins 1.610 1st error after 22 minutes, 1 error during 24 minutes Jenkins 1.617 1st error after 17 minutes, 2 errors during 27 minutes Jenkins 1.628 1st error after 12 minutes, 2 errors during 1 hour 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [docker-custom-build-environment-plugin] (JENKINS-30512) using ifconfig docker0 cannot get the IP address of the host for the docker command

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Spilker commented on  JENKINS-30512 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: using ifconfig docker0 cannot get the IP address of the host for the docker command  
 
 
 
 
 
 
 
 
 
 
Ah, right. Something like this should do: 

 

java.net.NetworkInterface docker0 = java.net.NetworkInterface.getByName('docker0');
String ip = docker0.getInterfaceAddresses().get(0).getAddress().getHostAddress();
 

 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [xfpanel-plugin] (JENKINS-23525) Crash when using Folders plugin: com.cloudbees.hudson.plugins.folder.Folder cannot be cast to hudson.model.Job

2015-09-18 Thread tomaszbech...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomasz Bech commented on  JENKINS-23525 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Crash when using Folders plugin: com.cloudbees.hudson.plugins.folder.Folder cannot be cast to hudson.model.Job  
 
 
 
 
 
 
 
 
 
 
I've fixed 'configuration' view and folder icon is hidden on xfpanel view. However Folders are using own containers for jobs - so there can be some issues there, but baiscally xfpanel view created in the folder should work. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [job-dsl-plugin] (JENKINS-30523) expose configure{} for steps

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Spilker commented on  JENKINS-30523 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: expose configure{} for steps  
 
 
 
 
 
 
 
 
 
 
You can use multiple steps with configure blocks in between to preserve the order. 

 

job('example') {
  steps {
shell('echo first')
  }
  configure { project ->
// ...
  }
  steps {
shell('echo last')
  }
}
 

 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [workflow-plugin] (JENKINS-30519) Declarative job properties in multibranch

2015-09-18 Thread magnus.jacobs...@netinsight.net (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 stephenconnolly commented on  JENKINS-30519 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Declarative job properties in multibranch  
 
 
 
 
 
 
 
 
 
 
I need to think over it some more, but I suspect this is closer to the "right" way to do things... may need minor tweaks along the way 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-30039) Regression in queue control in Jenkins 1.607: Build are executed concurrently although "Execute concurrent builds if necessary" is not ticked

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Magnus Jacobsson commented on  JENKINS-30039 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Regression in queue control in Jenkins 1.607: Build are executed concurrently although "Execute concurrent builds if necessary" is not ticked  
 
 
 
 
 
 
 
 
 
 
The results above are made with a freshly installed Jenkins in a separate test system. 
The same test case has produced around 30 errors during 2 days of testing in the production system with Jenkins version 1.628. 
We have seen the problem in real production testing at least 10 times since the upgrade to Jenkins 1.617 2015-06-10, but there are probable many more than has not been detected during the summer. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [cloudbees-folder-plugin] (JENKINS-30509) add id to Folder icon

2015-09-18 Thread tomaszbech...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomasz Bech closed an issue as Won't Fix 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
css selector did the trick, no need to change 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-30509 
 
 
 
  add id to Folder icon  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tomasz Bech 
 
 
 

Status:
 
 Open Closed 
 
 
 

Resolution:
 
 Won't Fix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [xfpanel-plugin] (JENKINS-23525) Crash when using Folders plugin: com.cloudbees.hudson.plugins.folder.Folder cannot be cast to hudson.model.Job

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-23525 
 
 
 
  Crash when using Folders plugin: com.cloudbees.hudson.plugins.folder.Folder cannot be cast to hudson.model.Job  
 
 
 
 
 
 
 
 
 

Change By:
 
 SCM/JIRA link daemon 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [xfpanel-plugin] (JENKINS-23525) Crash when using Folders plugin: com.cloudbees.hudson.plugins.folder.Folder cannot be cast to hudson.model.Job

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-23525 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Crash when using Folders plugin: com.cloudbees.hudson.plugins.folder.Folder cannot be cast to hudson.model.Job  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: tomaszbech Path: src/main/java/maps/hudson/plugin/xfpanel/XFPanelView.java src/main/resources/maps/hudson/plugin/xfpanel/XFPanelView/configure-entries.jelly src/main/resources/maps/hudson/plugin/xfpanel/XFPanelView/maindisplay.jelly http://jenkins-ci.org/commit/xfpanel-plugin/312109b162c551d2a7003c80724ac9bac07563d7 Log: [FIXED JENKINS-23525] 
Crash when using Folders plugin: com.cloudbees.hudson.plugins.folder.Folder cannot be cast to hudson.model.Job 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-30535) Jenkins logged in user info

2015-09-18 Thread bharat...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 bharat goel created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30535 
 
 
 
  Jenkins logged in user info  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 18/Sep/15 8:59 AM 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 bharat goel 
 
 
 
 
 
 
 
 
 
 
Hi Team 
i want to capture the jenkins logged in user . The details of the user that appear on the UI , right hand side of jenkins screen. This user is the logged in user and not necessarily would have started the build. I have tried Jenkins.getAuthentication().getName(); and User.Current().getDisplayName . But all of these return System as answer. I need to get the person's userid or name. Please suggest how to achieve this. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [container-slaves-plugin] (JENKINS-30537) move docker specific stuff into docker-slaves-plugin

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nicolas De Loof created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30537 
 
 
 
  move docker specific stuff into docker-slaves-plugin  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Nicolas De Loof 
 
 
 

Components:
 

 container-slaves-plugin 
 
 
 

Created:
 

 18/Sep/15 9:11 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Nicolas De Loof 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are

[JIRA] [container-slaves-plugin] (JENKINS-30537) move docker specific stuff into docker-slaves-plugin

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nicolas De Loof updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30537 
 
 
 
  move docker specific stuff into docker-slaves-plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Nicolas De Loof 
 
 
 

Component/s:
 
 docker-slaves-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-29340) E200015: ISVNAuthentication provider did not provide credentials

2015-09-18 Thread rec...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29340 
 
 
 
  E200015: ISVNAuthentication provider did not provide credentials  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Status:
 
 Reopened Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-29340) E200015: ISVNAuthentication provider did not provide credentials

2015-09-18 Thread rec...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29340 
 
 
 
  E200015: ISVNAuthentication provider did not provide credentials  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [job-dsl-plugin] (JENKINS-30523) expose configure{} for steps

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou commented on  JENKINS-30523 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: expose configure{} for steps  
 
 
 
 
 
 
 
 
 
 
Is it processed successively? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [saml-plugin] (JENKINS-29086) User IDs are case sensitive in saml-plugin

2015-09-18 Thread 0xc...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikhail Tyuzin commented on  JENKINS-29086 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: User IDs are case sensitive in saml-plugin  
 
 
 
 
 
 
 
 
 
 
Well, case sensitivity is context of SAML plugin makes sense only when it comes down to RBS. When SAML plugin receives a response, it does several things: 1) Creates local session for the user with ID=Subject from SAML response (original case from SAML is preserved) 2) Updates user name if necessary (original case from SAML is preserved) 3) Creates authorities collection from groups attribute of SAML message if any (original case from SAML is preserved) Then, information from #2 becomes visible on UI as user name, case sensitivity here is ok. As for #1 and #3, this data can be used in RBA and that is where case sensitivity plays negative role because it forces users to write case sensitive user ids and group names. Regarding case sensitivity for SAML data - no, there is no way for SP to tell IdP how to format the data, however most IdPs can control that on their side. But, no matter where/on what side toLower or toUpper is executed for "user id" and "group" attributes, this will not solve original problem. Even if plugin or IdP transform everything to lower case, when user gives some rights in RBS to user "petr_ina...@company.com", this rule simply wan't work whereas requester wanted this rule to be ok. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-30549) Symlink checkouts are not being preserved

2015-09-18 Thread gstock.pub...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 aflat created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30549 
 
 
 
  Symlink checkouts are not being preserved  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 subversion-plugin 
 
 
 

Created:
 

 18/Sep/15 7:14 PM 
 
 
 

Environment:
 

 Subversion plugin: 2.5.3  Jenkins version: 1.620  java 1.7.0  Master: centos 6.5  Slave centos 6.5 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 aflat 
 
 
 
 
 
 
 
 
 
 
I have symlinks checked into svn. When a do a svn checkout from the command line, they are treated as symlinks. When I use jenkins to check them out, they are converted into text files, with the contents being the correct symlink pointers. I need them to be symlinks again. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [kpp-management-plugin] (JENKINS-30550) Allow Storing Member Center Provisioning Profile Name

2015-09-18 Thread br...@l4mobile.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brett McGinnis created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30550 
 
 
 
  Allow Storing Member Center Provisioning Profile Name  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 kpp-management-plugin 
 
 
 

Created:
 

 18/Sep/15 7:45 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Brett McGinnis 
 
 
 
 
 
 
 
 
 
 
http://www.thecave.com/2014/09/16/using-xcodebuild-to-export-a-ipa-from-an-archive/ 
According to this article the -exportProvisioningProfile field requires the name of the provisioning profile name from Apple Member Center. 
When storing a provisioning profile there should be a text field for storing this information, and then later retrieving it at build time. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [jira-plugin] (JENKINS-28453) No known JIRA project corresponding to id: 'RCFOPS-112'

2015-09-18 Thread jbla...@kickflop.net (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jeff Blaine commented on  JENKINS-28453 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: No known JIRA project corresponding to id: 'RCFOPS-112'  
 
 
 
 
 
 
 
 
 
 
Will do. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [job-dsl-plugin] (JENKINS-30548) Post build step not removed from generated Maven job

2015-09-18 Thread gangadhar.chalap...@appdynamics.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Yoann Dubreuil created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30548 
 
 
 
  Post build step not removed from generated Maven job  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Daniel Spilker 
 
 
 

Components:
 

 job-dsl-plugin 
 
 
 

Created:
 

 18/Sep/15 7:00 PM 
 
 
 

Environment:
 

 core 1.609.3  job-dsl-plugin 1.38  maven-plugin 2.12 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Yoann Dubreuil 
 
 
 
 
 
 
 
 
 
 
Removing postBuildSteps block from a job-dsl script does not remove the post build step on the generated job. To reproduce, create a job-dsl seed job with this script: 

 

mavenJob('example') {
  goals 'clean install'
  postBuildSteps { maven { goals "sonar:sonar -Psonar" } }
}
 

 
Remove postBuildSteps block and run job-dsl seed job again. Configuration page of generated job example will still contain the post build step. 
On disk config.xml of generated job doesn't have  section anymore. Reloading generated job using a groovy script in system console doesn't help. Only restarting Jenkins works. That makes me think that the bug is in Maven plugin but not in JobDSL plugin. Something is wrong when reloading config.xml of generated job.

[JIRA] [perforce-plugin] (JENKINS-9819) Add support for p4 sync -p flag

2015-09-18 Thread gstock.pub...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 aflat closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-9819 
 
 
 
  Add support for p4 sync -p flag  
 
 
 
 
 
 
 
 
 

Change By:
 
 aflat 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [saml-plugin] (JENKINS-29086) User IDs are case sensitive in saml-plugin

2015-09-18 Thread bren...@letrabb.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brantone commented on  JENKINS-29086 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: User IDs are case sensitive in saml-plugin  
 
 
 
 
 
 
 
 
 
 
Working on that aspect (more political than technical  ). The PR work-around was because I could wait, needed to get it forced to lower-case. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-15355) AdjunctManager: exception upon startup

2015-09-18 Thread db...@cloudbees.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-15355 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: AdjunctManager: exception upon startup  
 
 
 
 
 
 
 
 
 
 
It's a warning related to the UI not being initialized while it's already being accessed. It's not fatal. Not sure whether stephenconnolly intended for this to be fixed. It is logged, but the fix should be in 1.607. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [saml-plugin] (JENKINS-29086) User IDs are case sensitive in saml-plugin

2015-09-18 Thread bren...@letrabb.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brantone commented on  JENKINS-29086 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: User IDs are case sensitive in saml-plugin  
 
 
 
 
 
 
 
 
 
 
Submitted PR https://github.com/jenkinsci/saml-plugin/pull/4 to provide a config option that "converts" the returned user id from SAML into a specific case. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4-plugin] (JENKINS-30425) Change information unavailable when using workflow plugin

2015-09-18 Thread mr...@sjm.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Rose commented on  JENKINS-30425 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Change information unavailable when using workflow plugin  
 
 
 
 
 
 
 
 
 
 
Installing https://jenkins.ci.cloudbees.com/job/plugins/job/p4-plugin/241 produces the following error for all of my project (matrix and workflow). 

Started by upstream project "re/review_main" build number 652 originally caused by: Started by user Michael Rose Building remotely on brhel7ac (x86_64-Linux-RHEL7 linux) in workspace /jenkins/workspace/re/review_main/ARCH/x86_64-Linux-RHEL7/BUILDSYSTEM/p4b/FORM/gcc (p4):cmd:... p4 client -o jenkins-brhel7ac-re-review_main-ARCH-x86_64-Linux-RHEL7-BUILDSYSTEM-p4___ p4 client -o jenkins-brhel7ac-re-review_main-ARCH-x86_64-Linux-RHEL7-BUILDSYSTEM-p4b-FORM-gcc 
(p4):stop:5 
P4 Task: establishing connection. ... server: foo ... node: bar (p4):cmd:... p4 info p4 info 
(p4):stop:6 (p4):cmd:... p4 client -o jenkins-brhel7ac-re-review_main-ARCH-x86_64-Linux-RHEL7-BUILDSYSTEM-p4___ p4 client -o jenkins-brhel7ac-re-review_main-ARCH-x86_64-Linux-RHEL7-BUILDSYSTEM-p4b-FORM-gcc 
(p4):stop:7 (p4):cmd:... p4 client -i p4 client -i 
Client jenkins-brhel7ac-re-review_main-ARCH-x86_64-Linux-RHEL7-BUILDSYSTEM-p4b-FORM-gcc saved. 
(p4):stop:8 (p4):cmd:... p4 client -o jenkins-brhel7ac-re-review_main-ARCH-x86_64-Linux-RHEL7-BUILDSYSTEM-p4___ p4 client -o jenkins-brhel7ac-re-review_main-ARCH-x86_64-Linux-RHEL7-BUILDSYSTEM-p4b-FORM-gcc 
(p4):stop:9 (p4):cmd:... p4 client -i p4 client -i 
Client jenkins-brhel7ac-re-review_main-ARCH-x86_64-Linux-RHEL7-BUILDSYSTEM-p4b-FORM-gcc saved. 
(p4):stop:10 ... client: jenkins-brhel7ac-re-review_main-ARCH-x86_64-Linux-RHEL7-BUILDSYSTEM-p4b-FORM-gcc (p4):cmd:... p4 client -o jenkins-brhel7ac-re-review_main-ARCH-x86_64-Linux-RHEL7-BUILDSYSTEM-p4___ p4 client -o jenkins-brhel7ac-re-review_main-ARCH-x86_64-Linux-RHEL7-BUILDSYSTEM-p4b-FORM-gcc 
(p4):stop:5 (p4):cmd:... p4 counter change p4 counter change 
(p4):stop:6 (p4):cmd:... p4 changes -m1 //jenkins-brhel7ac-re-review_main-ARCH-x86_64-Linux-RHEL7-BUILDSYSTE___ p4 changes -m1 //jenkins-brhel7ac-re-review_main-ARCH-x86_64-Linux-RHEL7-BUILDSYSTEM-p4b-FORM-gcc/... 
Change 141791 on 2015/09/18 by ecrist@re-main 'User should be allowed to set o' (p4):stop:7 Building on Node: brhel7ac java.io.IOException: remote file operation failed: /jenkins/workspace/re/review_main/ARCH/x86_64-Linux-RHEL7/BUILDSYSTEM/p4b/FORM/gcc at hudson.remoting.Channel@41314efb:brhel7ac: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@43109790 at hudson.FilePath.act(FilePath.java:987) at hudson.FilePath.act(FilePath.java:969) at org.jenkinsci.plugins.p4.PerforceScm.checkout(PerforceScm.java:331) at hudson.scm.SCM.checkout(SCM.java:485) at hudson.model.AbstractProject.checkout(AbstractProject.java:1276) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532) at hudson.model.Run.execute(Run.java:1744) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:98) at

[JIRA] [p4-plugin] (JENKINS-30425) Change information unavailable when using workflow plugin

2015-09-18 Thread mr...@sjm.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Rose edited a comment on  JENKINS-30425 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Change information unavailable when using workflow plugin  
 
 
 
 
 
 
 
 
 
 Installing https://jenkins.ci.cloudbees.com/job/plugins/job/p4-plugin/241 produces the following error for all of my  project  projects  (matrix and workflow).{quote}Started by upstream project "re/review_main" build number 652originally caused by: Started by user Michael RoseBuilding remotely on brhel7ac (x86_64-Linux-RHEL7 linux) in workspace /jenkins/workspace/re/review_main/ARCH/x86_64-Linux-RHEL7/BUILDSYSTEM/p4b/FORM/gcc(p4):cmd:... p4 client -o jenkins-brhel7ac-re-review_main-ARCH-x86_64-Linux-RHEL7-BUILDSYSTEM-p4___p4 client -o jenkins-brhel7ac-re-review_main-ARCH-x86_64-Linux-RHEL7-BUILDSYSTEM-p4b-FORM-gcc(p4):stop:5P4 Task: establishing connection server: foo... node: bar(p4):cmd:... p4 infop4 info(p4):stop:6(p4):cmd:... p4 client -o jenkins-brhel7ac-re-review_main-ARCH-x86_64-Linux-RHEL7-BUILDSYSTEM-p4___p4 client -o jenkins-brhel7ac-re-review_main-ARCH-x86_64-Linux-RHEL7-BUILDSYSTEM-p4b-FORM-gcc(p4):stop:7(p4):cmd:... p4 client -ip4 client -iClient jenkins-brhel7ac-re-review_main-ARCH-x86_64-Linux-RHEL7-BUILDSYSTEM-p4b-FORM-gcc saved.(p4):stop:8(p4):cmd:... p4 client -o jenkins-brhel7ac-re-review_main-ARCH-x86_64-Linux-RHEL7-BUILDSYSTEM-p4___p4 client -o jenkins-brhel7ac-re-review_main-ARCH-x86_64-Linux-RHEL7-BUILDSYSTEM-p4b-FORM-gcc(p4):stop:9(p4):cmd:... p4 client -ip4 client -iClient jenkins-brhel7ac-re-review_main-ARCH-x86_64-Linux-RHEL7-BUILDSYSTEM-p4b-FORM-gcc saved.(p4):stop:10... client: jenkins-brhel7ac-re-review_main-ARCH-x86_64-Linux-RHEL7-BUILDSYSTEM-p4b-FORM-gcc(p4):cmd:... p4 client -o jenkins-brhel7ac-re-review_main-ARCH-x86_64-Linux-RHEL7-BUILDSYSTEM-p4___p4 client -o jenkins-brhel7ac-re-review_main-ARCH-x86_64-Linux-RHEL7-BUILDSYSTEM-p4b-FORM-gcc(p4):stop:5(p4):cmd:... p4 counter changep4 counter change(p4):stop:6(p4):cmd:... p4 changes -m1 //jenkins-brhel7ac-re-review_main-ARCH-x86_64-Linux-RHEL7-BUILDSYSTE___p4 changes -m1 //jenkins-brhel7ac-re-review_main-ARCH-x86_64-Linux-RHEL7-BUILDSYSTEM-p4b-FORM-gcc/...Change 141791 on 2015/09/18 by ecrist@re-main 'User should be allowed to set o'(p4):stop:7Building on Node: brhel7acjava.io.IOException: remote file operation failed: /jenkins/workspace/re/review_main/ARCH/x86_64-Linux-RHEL7/BUILDSYSTEM/p4b/FORM/gcc at hudson.remoting.Channel@41314efb:brhel7ac: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@43109790 at hudson.FilePath.act(FilePath.java:987) at hudson.FilePath.act(FilePath.java:969) at org.jenkinsci.plugins.p4.PerforceScm.checkout(PerforceScm.java:331) at hudson.scm.SCM.checkout(SCM.java:485) at hudson.model.AbstractProject.checkout(AbstractProject.java:1276) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532) at hudson.model.Run.execute(Run.java:1744) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374)Caused by: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@43109790 at hudson.remoting.UserRequest.serialize(UserRequest.java:169) at hudson.remoting.UserRequest.(UserRequest.java:63) at hudson.remoting.Channel.call(Channel.java:751) at hudson.FilePath.act(FilePath.java:980) ... 11 moreCaused by: java.io.NotSerializableException: org.jenkinsci.plugins.p4.changes.P4Revision at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1183) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1547) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1508) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1431) at

[JIRA] [junit-plugin] (JENKINS-28394) Crash upon view results of build with junit test results

2015-09-18 Thread ashish.ya...@firemon.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ashish Yadav commented on  JENKINS-28394 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Crash upon view results of build with junit test results  
 
 
 
 
 
 
 
 
 
 
Are there any updates on this issue? We are having this issue too. Any root cause info? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [job-dsl-plugin] (JENKINS-30503) Gerrit event commentAdded() - Verdict Category not available in DSL

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gangadhar chalapaka commented on  JENKINS-30503 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Gerrit event commentAdded() - Verdict Category not available in DSL  
 
 
 
 
 
 
 
 
 
 
Thanks Daniel, I was under an impression that this is not documented. I will try with configure block.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [saml-plugin] (JENKINS-29086) User IDs are case sensitive in saml-plugin

2015-09-18 Thread 0xc...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikhail Tyuzin commented on  JENKINS-29086 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: User IDs are case sensitive in saml-plugin  
 
 
 
 
 
 
 
 
 
 
Will take a look on weekend. But as I wrote above, this will not really fix the problem mentioned by requester and this can be easily done on IdP side. If introduce such a feature, it should be possible to apply it for both user id and groups attributes separately. The reason is that starting from 0.4 release it is possible to configure all security related stuff using groups only, therefore user id case becomes absolutely non critical. And by the way, I have never seen such a setting in any system integrated with SAML IdP. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [build-pipeline-plugin] (JENKINS-22800) Downstream build does not wait for upstream build to complete

2015-09-18 Thread swatz...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Swathi Venkatachala commented on  JENKINS-22800 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Downstream build does not wait for upstream build to complete  
 
 
 
 
 
 
 
 
 
 
We observed this behavior too. When we enabled the following, on the parent job (Job A) 

 
Post-build Actions
Build other projects : Job B
 	Projects to build		
 		(*)Trigger only if build is stable
 

 
Job B did wait until the upstream job finished its build.  Hope this helps! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-client-plugin] (JENKINS-21116) Git Publisher does not use Credentials

2015-09-18 Thread mark.earl.wa...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-21116 
 
 
 
  Git Publisher does not use Credentials  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mark Waite 
 
 
 

Resolution:
 
 Not A Defect 
 
 
 

Status:
 
 Closed Reopened 
 
 
 

Assignee:
 
 Nicolas De Loof Mark Waite 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-plugin] (JENKINS-26582) ISE from RunMap.put using /git/notifyCommit on a matrix project

2015-09-18 Thread mark.earl.wa...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite commented on  JENKINS-26582 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: ISE from RunMap.put using /git/notifyCommit on a matrix project  
 
 
 
 
 
 
 
 
 
 
Usually, isolating a problem to root cause needs enough description of the distinct conditions which caused the problem so that someone else can duplicate the problem. 
In this case, it may need a support bundle (to show the versions of various plugins installed), a copy of the job definition (or a detailed enough description of the job definition that someone can recreate the job from that description), and a description of the actions taken to show the problem. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [email-ext-plugin] (JENKINS-30542) Enable the use of UpstreamComitterRecipientProvider for extendedEmail

2015-09-18 Thread glance+jenk...@acc.umu.se (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anton Lundin created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30542 
 
 
 
  Enable the use of UpstreamComitterRecipientProvider for extendedEmail  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Alex Earl 
 
 
 

Components:
 

 email-ext-plugin, job-dsl-plugin 
 
 
 

Created:
 

 18/Sep/15 11:30 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Anton Lundin 
 
 
 
 
 
 
 
 
 
 
I would like to be able to configure the UpstreamComitterRecipientProvider from the jenkins job dsl. 
It's just a RecipientProvider just like the others. 
Two other RecipientProviders that maybe should be added at the same time are: FailingTestSuspectsRecipientProvider FirstFailingBuildSuspectsRecipientProvider 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [job-dsl-plugin] (JENKINS-30541) fail on error

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30541 
 
 
 
  fail on error  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kanstantsin Shautsou 
 
 
 
 
 
 
 
 
 
 Job dsl step doesn't fail when dsl script doesn't exist, it just silently continue executing  it  job and ends with SUCCESSFUL build state . 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [email-ext-plugin] (JENKINS-30542) Enable the use of UpstreamComitterRecipientProvider for extendedEmail

2015-09-18 Thread slide.o....@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Earl assigned an issue to Daniel Spilker 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Assigning to Daniel since this is for job-dsl 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-30542 
 
 
 
  Enable the use of UpstreamComitterRecipientProvider for extendedEmail  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Earl 
 
 
 

Assignee:
 
 Alex Earl Daniel Spilker 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [job-dsl-plugin] (JENKINS-29600) Add support for the Docker Build and Publish Plugin.

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-29600 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add support for the Docker Build and Publish Plugin.  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Daniel Spilker Path: docs/Home.md job-dsl-core/src/main/docs/examples/javaposse/jobdsl/dsl/helpers/step/StepContext/dockerBuildAndPublish.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/DockerBuildAndPublishContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/StepContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/step/StepContextSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/7ac46019cf4281447fe0f689711e954987892287 Log: Merge pull request #621 from daspilker/

JENKINS-29600
 


JENKINS-29600
 added support for the CloudBees Docker Build and Publish plugin 
Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/339b6635b4ce...7ac46019cf42 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [job-dsl-plugin] (JENKINS-29600) Add support for the Docker Build and Publish Plugin.

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29600 
 
 
 
  Add support for the Docker Build and Publish Plugin.  
 
 
 
 
 
 
 
 
 

Change By:
 
 SCM/JIRA link daemon 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [job-dsl-plugin] (JENKINS-29600) Add support for the Docker Build and Publish Plugin.

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-29600 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add support for the Docker Build and Publish Plugin.  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Daniel Spilker Path: docs/Home.md job-dsl-core/src/main/docs/examples/javaposse/jobdsl/dsl/helpers/step/StepContext/dockerBuildAndPublish.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/DockerBuildAndPublishContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/StepContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/step/StepContextSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/3a47f13d4102bddd737cf6424846dbd6c02cc826 Log: added support for the CloudBees Docker Build and Publish plugin 
[FIXED JENKINS-29600] 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-plugin] (JENKINS-26582) ISE from RunMap.put using /git/notifyCommit on a matrix project

2015-09-18 Thread prose...@voltdb.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 philip rosegay commented on  JENKINS-26582 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: ISE from RunMap.put using /git/notifyCommit on a matrix project  
 
 
 
 
 
 
 
 
 
 
didn't answer the question: what do you need to isolate to root cause? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [multijob-plugin] (JENKINS-30517) Plugin for getting the downstream job changes to the upstream job changes.

2015-09-18 Thread titto.tho...@assyst.in (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Titto Thomas updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30517 
 
 
 
   Plugin for getting the downstream job changes to the upstream job changes.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Titto Thomas 
 
 
 

Labels:
 
 Mutli-job plugins 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [job-dsl-plugin] (JENKINS-30523) expose configure{} for steps

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Spilker commented on  JENKINS-30523 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: expose configure{} for steps  
 
 
 
 
 
 
 
 
 
 
Yes, each of the top level methods (steps, publishers, configure, ...) is processed successively. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [workflow-plugin] (JENKINS-30510) Workflow job listening pull requests

2015-09-18 Thread william.macau...@baesystems.com (JIRA)

Title: Message Title

Jesse Glick commented on JENKINS-30510

Re: Workflow job listening pull requests

In our case, should be enough with tracking Pull Request in origin (without forks), but I don't know how to retrieve them.

What kind of job should I use? Some specific configuration?

Just a multibranch workflow job with a Git branch source should suffice, since it will fetch all heads from the remote repository into a local cache clone and detect them there. Jenkins will create buildable subprojects for the branches it finds whether they were filed as PRs or not. In this case the PR can be used simply as a convenient place to track and comment on proposed changes from people who had push access anyway. Remember that the marker for a buildable branch is one which contains a Workflow script named Jenkinsfile at top level.
I have not recently tested this configuration against GitHub repositories specifically, since we have been working on a GitHub-optimized branch source. The basic plugin (which supports origin branches, so can build nonforked PRs like the generic Git branch source) is under internal development at the moment but I hope to have it released on @jenkinsci as soon as we can sort out the details of packaging and naming.

Add Comment

This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [job-dsl-plugin] (JENKINS-30543) Enable the usage of regular expressions in the tasks publisher

2015-09-18 Thread glance+jenk...@acc.umu.se (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anton Lundin created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30543 
 
 
 
  Enable the usage of regular expressions in the tasks publisher  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Daniel Spilker 
 
 
 

Components:
 

 job-dsl-plugin, tasks-plugin 
 
 
 

Created:
 

 18/Sep/15 11:33 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Anton Lundin 
 
 
 
 
 
 
 
 
 
 
The tasks plugin can accept the patterns to search for as regular expressions by setting the asRegexp flag to true. 
It would be great if one could set that flag from the jenkins-job-dsl. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [job-dsl-plugin] (JENKINS-30544) Enable setting id and url for deployArtifacts publisher

2015-09-18 Thread glance+jenk...@acc.umu.se (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anton Lundin created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30544 
 
 
 
  Enable setting id and url for deployArtifacts publisher  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Daniel Spilker 
 
 
 

Components:
 

 job-dsl-plugin, maven-plugin 
 
 
 

Created:
 

 18/Sep/15 11:36 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Anton Lundin 
 
 
 
 
 
 
 
 
 
 
To get the deployArtifacts (hudson.maven.RedeployPublisher) publisher to deploy artifacts to another repo than the default one, you need to set the id and url of that repo. 
It would be great if one could set those from the jenkins job dsl. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [active-choices-plugin] (JENKINS-30545) Active Choices Plugin: Bug with radio boxes

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Macauley created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30545 
 
 
 
  Active Choices Plugin: Bug with radio boxes  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Bruno P. Kinoshita 
 
 
 

Attachments:
 

 config.xml 
 
 
 

Components:
 

 active-choices-plugin 
 
 
 

Created:
 

 18/Sep/15 12:33 PM 
 
 
 

Environment:
 

 Active Choices Plugin v1.2 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 William Macauley 
 
 
 
 
 
 
 
 
 
 
Radio buttons with a default option do not create a variable with this option unless they are interacted with.  
To reproduce:  Using the attached config.xml: Click build with parameters Select an option for test_var_a, do not interact with radio buttons for test_var_b Click build 
Expected result: Build runs, with environmental variables test_var_a =  and test_var_b = opt_1 
Actual result: Build runs, with environmental variable test_var_a =  but no test_var_b environment value

[JIRA] [job-dsl-plugin] (JENKINS-29600) Add support for the Docker Build and Publish Plugin.

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Spilker commented on  JENKINS-29600 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add support for the Docker Build and Publish Plugin.  
 
 
 
 
 
 
 
 
 
 
Will be released in 1.39. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [job-dsl-plugin] (JENKINS-30541) fail on error

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30541 
 
 
 
  fail on error  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Daniel Spilker 
 
 
 

Components:
 

 job-dsl-plugin 
 
 
 

Created:
 

 18/Sep/15 10:28 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Kanstantsin Shautsou 
 
 
 
 
 
 
 
 
 
 
Job dsl step doesn't fail when dsl script doesn't exist, it just silently continue executing it. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[JIRA] [git-client-plugin] (JENKINS-21116) Git Publisher does not use Credentials

2015-09-18 Thread m...@andrey-belyaevskiy.ru (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrey Belyaevskiy closed an issue as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
I found that my key I use for repo clone have read only access in Stash repository as described in http://stackoverflow.com/questions/32627821/push-tag-to-stash-for-successfull-build-in-jenkins-fails-with-code-128-and-error/32643868#32643868. After I changed key to RW one all works fine.  
I'm Sorry for wrong re-open. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-21116 
 
 
 
  Git Publisher does not use Credentials  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andrey Belyaevskiy 
 
 
 

Status:
 
 Reopened Closed 
 
 
 

Resolution:
 
 Not A Defect 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [job-dsl-plugin] (JENKINS-30523) expose configure{} for steps

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou commented on  JENKINS-30523 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: expose configure{} for steps  
 
 
 
 
 
 
 
 
 
 
Then it will work, but code wouldn't look so elegant 

 


job('example') {
  steps {
shell('echo first')
configure { steps ->
// ...
}
shell('echo last')
  }
}
 

 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module

2015-09-18 Thread r...@kamstrup.dk (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rasmus Pedersen commented on  JENKINS-23271 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Intermittent Invalid Object ID in remoting module  
 
 
 
 
 
 
 
 
 
 
I'm experiencing this on 1.609.3 on a Windows Server 2008 R2 running a Jenkins slave as a service. I've only seen it on matrix builds. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-client-plugin] (JENKINS-21116) Git Publisher does not use Credentials

2015-09-18 Thread mark.earl.wa...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Thanks for the update. I'm glad that it is still fixed. 
I dream of someday finding a way to provide better diagnostics for permission errors. Most permission errors can have multiple causes, and the process to evaluate to root cause can be quite complex, but it seems like it would be possible, and would be much more user friendly if several possible causes could be suggested. 
In your case, the root cause analysis would need to realize that reading the repository was successful, but writing the repository failed. In other cases, the problem could be an incorrect private key, or the wrong public key being registered with the server, or the wrong host key being recorded on the client, or many other causes. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-21116 
 
 
 
  Git Publisher does not use Credentials  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mark Waite 
 
 
 

Status:
 
 Reopened Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[JIRA] [core] (JENKINS-30039) Regression in queue control in Jenkins 1.607: Build are executed concurrently although "Execute concurrent builds if necessary" is not ticked

2015-09-18 Thread db...@cloudbees.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-30039 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Regression in queue control in Jenkins 1.607: Build are executed concurrently although "Execute concurrent builds if necessary" is not ticked  
 
 
 
 
 
 
 
 
 
 
stephenconnolly Could you take a look at this? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-30039) Regression in queue control in Jenkins 1.607: Build are executed concurrently although "Execute concurrent builds if necessary" is not ticked

Title: Message Title

stephenconnolly commented on JENKINS-30039

Re: Regression in queue control in Jenkins 1.607: Build are executed concurrently although "Execute concurrent builds if necessary" is not ticked

OK I think I know what is going on...
So Queue.maintain() starts each task sequentially and updates the queue snapshot after each task is submitted so that Task.isBuildBlocked() can reflect the now running tasks...
For AbstractProject children, the critical part is that we end up calling Job.isLogUpdated: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Job.java#L317
This is going to look at the last build and see what state it is in...
So here is the race condition I see:
1. Queue.maintain() has two builds of the Job (I do not believe this issue is restricted to MatrixProject. I suspect any parameterized job will have the same issue) in the queue. 2. Because the job is not currently building, both entries are "buildable" 3. We get down to https://github.com/jenkinsci/jenkins/blob/c9c62d3681460d4898f26e8fe07b9d4fc80f40e7/core/src/main/java/hudson/model/Queue.java#L1461 with both requests in buildables 4. The first one gets picked up and passes through https://github.com/jenkinsci/jenkins/blob/c9c62d3681460d4898f26e8fe07b9d4fc80f40e7/core/src/main/java/hudson/model/Queue.java#L1464 and it is submitted to the assigned executor 5. The assigned executor is waiting for the Queue lock: https://github.com/jenkinsci/jenkins/blob/c9c62d3681460d4898f26e8fe07b9d4fc80f40e7/core/src/main/java/hudson/model/Executor.java#L317 6. We loop back around and pick up the second request for the job. 7. The second request gets through https://github.com/jenkinsci/jenkins/blob/c9c62d3681460d4898f26e8fe07b9d4fc80f40e7/core/src/main/java/hudson/model/Queue.java#L1464 because the first request has not reached https://github.com/jenkinsci/jenkins/blob/c9c62d3681460d4898f26e8fe07b9d4fc80f40e7/core/src/main/java/hudson/model/Executor.java#L335 yet so the last build is before either request.
Ugh! That is nasty... I also suspect it was always present as a bug anyway but it just is slightly easier to trigger now as the task creation is within the Queue lock and as a result we have forced some serialization...
I can think of two potential fix routes:
1. Only ever schedule one instance of a Task per Queue.maintain() that would let the other instances create their run 2. Make `Job.isLogUpdated()` check for the project being assigned as a WorkUnit to any Node as a fallback if it thinks the log is not still being updated.
I suspect the 2nd is the more correct implementation, but I'd need to think it through more fully. The 1st is just a hack (but probably a quick one) and would be at the vagrancy of the JVM's thread scheduler (i.e. it assumes fairness which is a mistake to assume)

Add Comment

[JIRA] [container-slaves-plugin] (JENKINS-30536) Allow user to configure a container to run some build steps in a (distinct) container

2015-09-18 Thread magnus.jacobs...@netinsight.net (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nicolas De Loof created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30536 
 
 
 
  Allow user to configure a container to run some build steps in a (distinct) container  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Nicolas De Loof 
 
 
 

Components:
 

 container-slaves-plugin 
 
 
 

Created:
 

 18/Sep/15 9:09 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Nicolas De Loof 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You

[JIRA] [core] (JENKINS-30039) Regression in queue control in Jenkins 1.607: Build are executed concurrently although "Execute concurrent builds if necessary" is not ticked

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Magnus Jacobsson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30039 
 
 
 
  Regression in queue control in Jenkins 1.607: Build are executed concurrently although "Execute concurrent builds if necessary" is not ticked  
 
 
 
 
 
 
 
 
 

Change By:
 
 Magnus Jacobsson 
 
 
 

Summary:
 
 Regression in queue control in Jenkins 1.607: Build are executed concurrently although "Execute concurrent builds if necessary" is not ticked 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [jira-plugin] (JENKINS-23139) Jenkins not displaying Versions in dropdown

2015-09-18 Thread radek.anton...@quiddia.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Radek Antoniuk resolved as Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Thanks! 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-23139 
 
 
 
  Jenkins not displaying Versions in dropdown  
 
 
 
 
 
 
 
 
 

Change By:
 
 Radek Antoniuk 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [docker-custom-build-environment-plugin] (JENKINS-30512) using ifconfig docker0 cannot get the IP address of the host for the docker command

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Yoann Dubreuil commented on  JENKINS-30512 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: using ifconfig docker0 cannot get the IP address of the host for the docker command  
 
 
 
 
 
 
 
 
 
 
Following Daniel Spilker idea, I wrote a fix using native Java API in PR-32 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-30480) documentation of any change in build configuration

2015-09-18 Thread cobe...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Obexer commented on  JENKINS-30480 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: documentation of any change in build configuration  
 
 
 
 
 
 
 
 
 
 
Should be possible with: https://wiki.jenkins-ci.org/display/JENKINS/SCM+Sync+configuration+plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [groovy-postbuild-plugin] (JENKINS-26918) Workflow support for Groovy Postbuild

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick commented on  JENKINS-26918 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Workflow support for Groovy Postbuild  
 
 
 
 
 
 
 
 
 
 
See the guide for general tips, but this plugin is probably more of a special case. (Turning GroovyPostbuildRecorder into a SimpleBuildStep would not work well.) 
It is not obvious to me what aspects of the plugin are useful to support from Workflow. You can already run Groovy code of your choice, and update the build description: 

 

currentBuild.description = "This was building ${someComputedValue}!"
 

 
So we need to clearly determine which features are unique to this plugin—previously mentioned were badges and summary actions—and decide on a reasonably intuitive way of exposing those to Workflow scripts. 
The simplest approach would be to update BadgeManager to support Run rather than only AbstractBuild, then expose it using the GlobalVariable extension point as manager. Then from Workflow you could use essentially the same syntax as in a post-build script from a freestyle project: 

 

manager.addWarningBadge 'Lots of tests skipped, watch out!'
 

 
There is a catch: to find the build associated with the CpsScript would seem to require an API change, as seen by this use of package access. I actually introduced such an API in an aborted attempt to solve JENKINS-30222: 

 

diff --git a/cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsScript.java b/cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsScript.java
index 69a24c9..23501bf 100644
--- a/cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsScript.java
+++ b/cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsScript.java
@@ -136,6 +140,10 @@ public abstract class CpsScript extends SerializableScript {
 }
 }
 
+public CpsFlowExecution $execution() {
+return execution;
+}
+
 @Override
 public Object evaluate(String script) throws CompilationFailedException {
 // this might throw the magic CpsCallableInvocation to execute the script asynchronously
 

 
A more integrated approach would be to create an extension point so that RunWrapper (used for currentBuild in core Workflow) could be given additional methods and properties by plugins, so that you could write 

 

currentBuild.addWarningBadge 'Lots of tests skipped, watch out!'
 

 
but this would be more work and require more knowledge of Groovy intricacies.

[JIRA] [git-plugin] (JENKINS-26582) ISE from RunMap.put using /git/notifyCommit on a matrix project

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick commented on  JENKINS-26582 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: ISE from RunMap.put using /git/notifyCommit on a matrix project  
 
 
 
 
 
 
 
 
 
 
Right, ideally a way to reproduce the problem from scratch. When that cannot be found, there may be some clues that are helpful (for example: only happens when a certain plugin is installed/configured), but in general the problem may not be fixable. For certain bugs of course the error message/stack trace suffices to guess at a diagnosis. Unfortunately that is not the case here. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4-plugin] (JENKINS-30546) Template workspace does not copy 'Options:'

2015-09-18 Thread kwi...@perforce.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karl Wirth created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30546 
 
 
 
  Template workspace does not copy 'Options:'  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 p4-plugin 
 
 
 

Created:
 

 18/Sep/15 3:08 PM 
 
 
 

Environment:
 

 Jenkins ver. 1.629  p4-plugin 1.3.1  
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Karl Wirth 
 
 
 
 
 
 
 
 
 
 
Reproduction steps: (1) Create workspaces jenkins_template with allwrite and modtime options. (2) Set the 'Template workspace' in the build job to be jenkins_template. (3) Leave 'Workspace Name Format' as 'jenkins-$ {NODE_NAME} 
-$ {JOB_NAME} 
' (4) Run the build job 
New workspace will contain the correct view but none of the options will be copied. If you run 'p4 client -t jenkins_template test123' the 'test123' client will have the same options. 
Believe the options copying is missing from TemplateWorkspaceImpl.setClient.

[JIRA] [p4-plugin] (JENKINS-30546) Template workspace does not copy 'Options:'

2015-09-18 Thread kwi...@perforce.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karl Wirth updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30546 
 
 
 
  Template workspace does not copy 'Options:'  
 
 
 
 
 
 
 
 
 

Change By:
 
 Karl Wirth 
 
 
 
 
 
 
 
 
 
 Reproduction steps:(1) Create workspaces jenkins_template with allwrite and modtime options.(2) Set the 'Template workspace' in the build job to be jenkins_template.(3) Leave 'Workspace Name Format' as  'jenkins-${NODE_NAME}-${JOB_NAME}'  the default. (4) Run the build jobNew workspace will contain the correct view but none of the options willbe copied. If you run 'p4 client -t jenkins_template test123' the 'test123'client will have the same options.Believe the options copying is missing from TemplateWorkspaceImpl.setClient. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [docker-custom-build-environment-plugin] (JENKINS-30512) using ifconfig docker0 cannot get the IP address of the host for the docker command

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Yoann Dubreuil assigned an issue to Yoann Dubreuil 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30512 
 
 
 
  using ifconfig docker0 cannot get the IP address of the host for the docker command  
 
 
 
 
 
 
 
 
 

Change By:
 
 Yoann Dubreuil 
 
 
 

Assignee:
 
 Nicolas De Loof Yoann Dubreuil 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [docker-custom-build-environment-plugin] (JENKINS-30512) using ifconfig docker0 cannot get the IP address of the host for the docker command

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Yoann Dubreuil started work on  JENKINS-30512 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Yoann Dubreuil 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4-plugin] (JENKINS-29598) p4 polling doesn't trigger workflow

2015-09-18 Thread magnus.jacobs...@netinsight.net (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick commented on  JENKINS-29598 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: p4 polling doesn't trigger workflow  
 
 
 
 
 
 
 
 
 
 
Optimistically linking; link can be removed if it is shown to be incorrect. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Hot REQ Today Interview Role : HP Voltage Key Management Consultant Location: Atlanta, GA and Austin, TX

2015-09-18 Thread Reddappa Reddy

*HI,*

*Hello,*



*Hope you are doing good!*

*This is very urgent opening. Please send your available matching
candidates on redd...@intellilinktech.com *



*IMMEDIATE INTERVIEW AND MUST NEEDED H1B AND PHOTO ID.*



*Role : **HP Voltage Key Management Consultant*

*Location: Atlanta, GA and Austin, TX*

*Duration : **12 months contract*

*Client: RETAILER |*



· HP Security Voltage Security consultant, maintaining quality and
customer satisfaction.

o   Develops solutions and technically lead their implementation at
customer locations

o   Experienced in giving permission to decrypt or de-tokenize on a
application or user basis

o   Manage build out of frameworks for HP Voltage SecureData

o   Manage relationship with HP Voltage SecureData

o   Create a role based access to data at a data field level, mapping
directly to enterprise data access rules and policies.

o   Working closely with Customer's Security Team to develop Security
Solutions, either at customer location or remotely dependent upon the
customer's requirements and preferred working practices.

· Provide assistance and support on security issues to sales and
other team members as required to achieve overall benefits for the delivery
of services to the customer and company as a whole. Share technical
knowledge and experiences.




*Thank you,Reddy, Sr.Talent Acquisition SpecialistEmail:
redd...@intellilinktech.com
Gmail: reddy.usrecrui...@gmail.com
Ph: 732-400-1778 Ext:103IntelliLink
Technologies Edison NJ 08817- USA. *

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4-plugin] (JENKINS-28237) p4-plugin does not provide accurate polling results in workflow job

2015-09-18 Thread rpoc...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robby Pocase updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-28237 
 
 
 
  p4-plugin does not provide accurate polling results in workflow job  
 
 
 
 
 
 
 
 
 

Change By:
 
 Robby Pocase 
 
 
 

Environment:
 
 Jenkins 1.596.1workflow 1. 6 Snapshot  609.2 p4-plugin 1. 2.2 Snapshot 10 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4-plugin] (JENKINS-29598) p4 polling doesn't trigger workflow

2015-09-18 Thread rpoc...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robby Pocase commented on  JENKINS-29598 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: p4 polling doesn't trigger workflow  
 
 
 
 
 
 
 
 
 
 
This is still an issue in p4-plugin 1.3.1. 
Possible duplicate of: https://issues.jenkins-ci.org/browse/JENKINS-28237 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [global-build-stats-plugin] (JENKINS-15969) Build Stats Plugin Returns so much data it hangs

2015-09-18 Thread gray...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Gray commented on  JENKINS-15969 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Build Stats Plugin Returns so much data it hangs  
 
 
 
 
 
 
 
 
 
 
This is an old ticket, but just for the record, I'm seeing this too (global/build-stats/api/json?depth=2 returns insane amounts of data) : Jenkins ver. 1.596.2 Global Stats Plugin version: 1.3 I'm hesitant to delete my charts, but if that is the only way to make this plugin work, then I'll do it. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-30039) Regression in queue control in Jenkins 1.607: Build are executed concurrently although "Execute concurrent builds if necessary" is not ticked

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Magnus Jacobsson commented on  JENKINS-30039 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Regression in queue control in Jenkins 1.607: Build are executed concurrently although "Execute concurrent builds if necessary" is not ticked  
 
 
 
 
 
 
 
 
 
 
@stephenconnolly: Thanks for the thorough investigation. I'm looking forward to your fix. Better a thought through correct implementation that a quick hack  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-30039) Regression in queue control in Jenkins 1.607: Build are executed concurrently although "Execute concurrent builds if necessary" is not ticked

2015-09-18 Thread magnus.jacobs...@netinsight.net (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Magnus Jacobsson edited a comment on  JENKINS-30039 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Regression in queue control in Jenkins 1.607: Build are executed concurrently although "Execute concurrent builds if necessary" is not ticked  
 
 
 
 
 
 
 
 
 
 @stephenconnolly: Thanks for the thorough investigation. I'm looking forward to your fix. Better a thought through correct implementation  that  than  a quick hack :-) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [ec2-plugin] (JENKINS-27601) instance caps incorrectly calculated

2015-09-18 Thread tba...@circle.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Trevor Baker commented on  JENKINS-27601 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: instance caps incorrectly calculated  
 
 
 
 
 
 
 
 
 
 
It would be great to have a new release cut so we can start using this! Thanks! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [maven-plugin] (JENKINS-30360) jmeter-maven-plugin in hang state preventing job to finish properly

2015-09-18 Thread neillfon...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Neill Lima updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30360 
 
 
 
  jmeter-maven-plugin in hang state preventing job to finish properly  
 
 
 
 
 
 
 
 
 

Change By:
 
 Neill Lima 
 
 
 

Attachment:
 
 screenshot.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4-plugin] (JENKINS-28237) p4-plugin does not provide accurate polling results in workflow job

2015-09-18 Thread rpoc...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robby Pocase updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-28237 
 
 
 
  p4-plugin does not provide accurate polling results in workflow job  
 
 
 
 
 
 
 
 
 

Change By:
 
 Robby Pocase 
 
 
 

Environment:
 
 Jenkins 1. 596 609 . 1 2 workflow 1. 609.2 10 p4-plugin 1. 10 3.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-30039) Regression in queue control in Jenkins 1.607: Build are executed concurrently although "Execute concurrent builds if necessary" is not ticked

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 stephenconnolly commented on  JENKINS-30039 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Regression in queue control in Jenkins 1.607: Build are executed concurrently although "Execute concurrent builds if necessary" is not ticked  
 
 
 
 
 
 
 
 
 
 
https://github.com/jenkinsci/jenkins/pull/1834 implements my 2nd line of attack. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [job-dsl-plugin] (JENKINS-30127) Job DSL syntax should allow nextBuildNumber to be set at create/update time

2015-09-18 Thread r...@akom.net (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexander Komarov commented on  JENKINS-30127 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Job DSL syntax should allow nextBuildNumber to be set at create/update time  
 
 
 
 
 
 
 
 
 
 
Link to pull request for convenience: https://github.com/jenkinsci/job-dsl-plugin/pull/591 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [ssh-plugin] (JENKINS-24402) jsch version

2015-09-18 Thread valentino.s...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bhagyesh Shah commented on  JENKINS-24402 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: jsch version  
 
 
 
 
 
 
 
 
 
 
When would this fix be available for general download  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [packaging] (JENKINS-26240) Jenkins 1.595 cannot be installed on Ubuntu 10.04.x

2015-09-18 Thread db...@cloudbees.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-26240 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins 1.595 cannot be installed on Ubuntu 10.04.x  
 
 
 
 
 
 
 
 
 
 
James Nord I really don't see us fixing the situation for EOLed operating system releases. While someone could show up and provide a fix that works (unlike mine), we should probably resolve this as Won't Fix anyway. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [jira-plugin] (JENKINS-23139) Jenkins not displaying Versions in dropdown

2015-09-18 Thread j...@langevin.me (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jonathan Langevin commented on  JENKINS-23139 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins not displaying Versions in dropdown  
 
 
 
 
 
 
 
 
 
 
Radek Antoniuk, I don't recall what fixed the issue for me (since this was a year ago), but versions are working fine for me, with current stable Jenkins & current Jira releases. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [maven-plugin] (JENKINS-22252) Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap

2015-09-18 Thread edb...@java.net (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 edbras commented on  JENKINS-22252 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap  
 
 
 
 
 
 
 
 
 
 
Same here, using Jenkins v1.629, downgrading to Mvn integration plugin 2.9 solved it. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [job-dsl-plugin] (JENKINS-29600) Add support for the Docker Build and Publish Plugin.

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Spilker commented on  JENKINS-29600 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add support for the Docker Build and Publish Plugin.  
 
 
 
 
 
 
 
 
 
 
https://github.com/jenkinsci/job-dsl-plugin/pull/621 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [container-slaves-plugin] (JENKINS-30540) Use job listener instead of slave listener where possible