[JIRA] (JENKINS-15559) Build on every online node hangs up after all jobs are complete
Alex Vesely created JENKINS-15559 Build on every online node hangs up after all jobs are complete Issue Type: Bug Affects Versions: current Assignee: domi Components: nodelabelparameter Created: 18/Oct/12 6:05 AM Description: Noticing this issue since Jenkins 1.485. I have a job that runs instances of another job in parallel on all available nodes. The jobs start, each one finishes successfully, but the main job hangs indefinitely, as if waiting for something else to finish. During this, the queue is empty and the only running job is this 'master' job. Project: Jenkins Priority: Critical Reporter: Alex Vesely This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15527) update plugin
Ganesan Sambandam updated JENKINS-15527 update plugin Change By: Ganesan Sambandam (18/Oct/12 6:17 AM) Priority: Major Trivial This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15560) Lazy loading cause’s http links from other html pages into Jenkins do not work properly
Christian Grobauer created JENKINS-15560 Lazy loading cause’s http links from other html pages into Jenkins do not work properly Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 18/Oct/12 7:02 AM Description: In our environment we have an overview page which contains several links into some workspaces and console output of Jenkins jobs. Since the lazy loading feature is introduced the links do not work properly any more. Maybe it’s possible to make the Feature optional … Thanks, Christian Environment: Windows Server 2008 R2 - Apache Tomcat 7.0.2 Project: Jenkins Labels: jenkins Priority: Major Reporter: Christian Grobauer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15561) Downstream buildview does not show multiple instancies of a same job
Markus Strand created JENKINS-15561 Downstream buildview does not show multiple instancies of a same job Issue Type: Bug Assignee: shinodkm Components: downstream-buildview Created: 18/Oct/12 7:03 AM Description: If build A#1 triggers build B#1 on a buildstep and then build B#2 on another buildstep, only the latter B#2 will be shown on the downstream buildview. Project: Jenkins Priority: Major Reporter: Markus Strand This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15562) Support setting the client version
davidstrauss created JENKINS-15562 Support setting the client version Issue Type: Improvement Affects Versions: current Assignee: kutzi Components: ircbot Created: 18/Oct/12 7:30 AM Description: Currently, the client version gets set to a PircX string that isn't very friendly. It would be nice to be able to include more identifying information about the bot and its operators. Project: Jenkins Priority: Minor Reporter: davidstrauss This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15562) Support setting the client version
davidstrauss updated JENKINS-15562 Support setting the client version Change By: davidstrauss (18/Oct/12 7:32 AM) Description: Currently,theclient version getsset (changeablewiththesetVersioncall)defaults toaPircXstringthatisntveryfriendly.Itwouldbenicetobeabletoincludemoreidentifyinginformationaboutthebotanditsoperators. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15562) Support setting the client version
davidstrauss commented on JENKINS-15562 Support setting the client version Hi everyone. I need this bug/feature so much that I'm willing to pay 50.00 bucks for it. This offer is registered at FreedomSponsors (http://www.freedomsponsors.org/core/issue/44/support-setting-the-client-version). Once you solve it (according to the acceptance criteria described there), just create a FreedomSponsors account and mark it as resolved (oh, you'll need a Paypal account too) I'll then check it out and will gladly pay up! If anyone else would like to throw in a few bucks to elevate the priority on this issue, you should check out FreedomSponsors! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15242) org.objectweb.asm.ClassReader.accept error
Vlado Pakan closed JENKINS-15242 as Fixed org.objectweb.asm.ClassReader.accept error With version 1.0.8 it's working for me. Thank you a lot for quick response. Change By: Vlado Pakan (18/Oct/12 8:00 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15551) Release Plugin vs. M2 Release Plugin (work together?)
Hannes Kogler assigned JENKINS-15551 to Peter Hayes Release Plugin vs. M2 Release Plugin (work together?) a Change By: Hannes Kogler (18/Oct/12 8:43 AM) Assignee: teilo PeterHayes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15551) Release Plugin vs. M2 Release Plugin (work together?)
Hannes Kogler edited a comment on JENKINS-15551 Release Plugin vs. M2 Release Plugin (work together?) also the feature to automatically load the next versions and suggest them in the version fields I am missing in the "Release Plugin" whereas the "M2 Release Plugin" does a great job here. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15551) Release Plugin vs. M2 Release Plugin (work together?)
Hannes Kogler edited a comment on JENKINS-15551 Release Plugin vs. M2 Release Plugin (work together?) also the feature to automatically load the next versions and suggest them in the version fields I am missing in the "Release Plugin" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15551) Release Plugin vs. M2 Release Plugin (work together?)
Hannes Kogler edited a comment on JENKINS-15551 Release Plugin vs. M2 Release Plugin (work together?) also the feature to automatically load the next versions and suggest them in the version fields I am missing in the "Release Plugin" whereas the "M2 Release Plugin" does a great job here. Or do the two Plugins disturb each other when parallel installed?? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9913) Concurrent builds getting batched/nodes not getting released when jobs are completed
Xavier Leprévost commented on JENKINS-9913 Concurrent builds getting batched/nodes not getting released when jobs are completed I there any chance to have this fixed soon ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15563) NullPointerException when clicking More... link in Build History widget
Patrick Hancke created JENKINS-15563 NullPointerException when clicking More... link in Build History widget Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: jenkins-npe1.png, jenkins-npe2.png Components: core Created: 18/Oct/12 9:26 AM Description: When I click the 'More...' hyperlink in the Build History widget, I get a stack trace. See screenshots. Environment: On RHEL Project: Jenkins Priority: Major Reporter: Patrick Hancke This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13032) Updating cvs plugin to version 2.0 causes java.lang.RuntimeException: CVS authentication failure while running rlog command
Joël Royer reopened JENKINS-13032 Updating cvs plugin to version 2.0 causes java.lang.RuntimeException: CVS authentication failure while running rlog command I've got the same problem since version 2.0 of the plugin. I've got timeouts randomly. However, the CVS server is available, I can ping it from the jenkins server. Change By: Joël Royer (18/Oct/12 9:37 AM) Resolution: NotADefect Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13032) Updating cvs plugin to version 2.0 causes java.lang.RuntimeException: CVS authentication failure while running rlog command
Joël Royer edited a comment on JENKINS-13032 Updating cvs plugin to version 2.0 causes java.lang.RuntimeException: CVS authentication failure while running rlog command I've got the same problem since version 2.0 of the plugin. I've got timeouts randomly. However, the CVS server is available, I can ping it from the jenkins server. Windows Server 2003 / Glassfish 3.1.2.2 / Oracle SDK 1.7.0_07 / Jenkins 1.486 / CVS Plugin 2.0 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9693) maven.build.timestamp.format is not obeyed in maven builds
Tomi Savolainen commented on JENKINS-9693 maven.build.timestamp.format is not obeyed in maven builds Reproduced on Jenkins ver. 1.486 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15563) NullPointerException when clicking More... link in Build History widget
Richard Mortimer resolved JENKINS-15563 as Duplicate NullPointerException when clicking More... link in Build History widget Duplicate of JENKINS-15499 Change By: Richard Mortimer (18/Oct/12 10:16 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15565) Disk usage link broken in SSL
Michael Nadel created JENKINS-15565 Disk usage link broken in SSL Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: disk-usage Created: 18/Oct/12 11:16 AM Description: The left-hand nav links to a non-SSL "Disk usage" page even when running in SSL. Project: Jenkins Priority: Minor Reporter: Michael Nadel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15322) NOTESTS in TAP response gives parse error and stack trace from plugin
Alex Newnham commented on JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin Hi Bruno, here's another NOTESTS .tap file, generated from skip_all as detailed in http://search.cpan.org/~mschwern/Test-Simple-0.98/lib/Test/More.pm We also supplied a $skip_reason (specifically " No Relevant Tests as No DB Costs for RequestConfig2V11EncoreNew"). /opt/performance/scripts/t/dbcoststest1.t .. skipped: No Relevant Tests as No DB Costs for RequestConfig2V11EncoreNew Files=1, Tests=0, 1 wallclock secs ( 0.00 usr 0.01 sys + 0.55 cusr 0.06 csys = 0.62 CPU) Result: NOTESTS This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15566) Administrators should be able to revert a build's scoring
roxspring created JENKINS-15566 Administrators should be able to revert a builds scoring Issue Type: Improvement Assignee: redsolo Components: ci-game Created: 18/Oct/12 1:34 PM Description: Occasionally a build fails for environmental that are not the fault of any of the contributers. I would be nice if, as the administrator, I could redress this by picking a particular build and backing out its effect on the scoreboard. I used to be able to work around this by editing people's scores manually but can't do that any more thanks to JENKINS-3575. Project: Jenkins Priority: Major Reporter: roxspring This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15366) Problem displaying Jacoco coverage data in Jenkins for very large number of classes and methods.
Shane McEneaney reopened JENKINS-15366 Problem displaying Jacoco coverage data in Jenkins for very large number of classes and methods. Hi Ogi, I upgraded to the latest version (1.8) of the Jenkins Jacoco plugin and the problem still exists. I'm going to attach some screen shots. Can you take a look at it please? Thanks again, Shane Change By: Shane McEneaney (18/Oct/12 1:45 PM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15366) Problem displaying Jacoco coverage data in Jenkins for very large number of classes and methods.
Shane McEneaney updated JENKINS-15366 Problem displaying Jacoco coverage data in Jenkins for very large number of classes and methods. Problem still exists after upgrade of plugin and rebuild of project. Change By: Shane McEneaney (18/Oct/12 1:51 PM) Attachment: JacocoJenkinsPluginVersion.PNG This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15366) Problem displaying Jacoco coverage data in Jenkins for very large number of classes and methods.
Shane McEneaney updated JENKINS-15366 Problem displaying Jacoco coverage data in Jenkins for very large number of classes and methods. Problem still exists after upgrade of plugin and rebuild of project. Change By: Shane McEneaney (18/Oct/12 1:51 PM) Attachment: JacocoJenkinsProblemStillExists.PNG This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15366) Problem displaying Jacoco coverage data in Jenkins for very large number of classes and methods.
Shane McEneaney edited a comment on JENKINS-15366 Problem displaying Jacoco coverage data in Jenkins for very large number of classes and methods. Please see recently attached screenshots. Let me know if you need anything else. Thanks, Shane This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
Chris Welch commented on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel We consistently get this error on a Linux build slave consistently on jobs that have little output and take a long time (typically 2 hours). We are using ssh and I suspect the problem is due to no traffic on the ssh link for this long period. Using Jenkins 1.434. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15567) Ubuntu /etc/default/jenkins contains syntax error in sample command line arg
Jerry Preissler created JENKINS-15567 Ubuntu /etc/default/jenkins contains syntax error in sample command line arg Issue Type: Bug Assignee: Unassigned Components: core Created: 18/Oct/12 1:58 PM Description: Installed Jenkins 1.486 via the apt repository. /etc/default/jenkins contains the sample command line argument --argumentsRealm.$ADMIN_USER=admin This should rather read --argumentsRealm.roles.$ADMIN_USER=admin Environment: Ubuntu 12.10 Project: Jenkins Priority: Trivial Reporter: Jerry Preissler This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15568) The sections are misnamed and can't be collapsed in Internet Explorer 9
William Roberts created JENKINS-15568 The sections are misnamed and cant be collapsed in Internet Explorer 9 Issue Type: Bug Affects Versions: current Assignee: Dean Yu Components: collapsing-console-sections Created: 18/Oct/12 2:19 PM Description: All of my console sections show up with the title "Undefined" and no option to collapse them. When I use the IE9 Developer Tools to inspect the page, I can see that the section is div class="collapseHeader" ... and it contains a name="console-section-8" with a text part that says "undefined". Looking at the same Jenkins server and the same console from FireFox shows the correct name and the option to collapse the section. Environment: Browser is IE9, running on 64-bit Windows 7 Project: Jenkins Labels: IE9 Priority: Minor Reporter: William Roberts This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15569) draft-published trigger doesn't work
ickersep created JENKINS-15569 draft-published trigger doesnt work Issue Type: Bug Assignee: rsandell Components: gerrit-trigger Created: 18/Oct/12 2:27 PM Description: I can't get triggering on draft-published to work. Environment: Gerrit 2.5-rc1 Project: Jenkins Priority: Major Reporter: ickersep This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Darrell King created JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis Issue Type: Bug Affects Versions: current Assignee: Ognjen Bubalo Components: jacoco Created: 18/Oct/12 2:34 PM Description: In my Maven config there are a number of classes that are excluded from Jacoco analysis. The report generated by Jacoco does not include these classes. The report generated by the Jenkins Jacoco plugin does includes these classes which gives a misleading picture and makes it difficult to set any coverage thresholds. I think this may be related to JENKINS-14975. Project: Jenkins Labels: jacoco Priority: Minor Reporter: Darrell King This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15571) hudson-jacoco-plugin crashes if jacoco didn't run
Christoph B created JENKINS-15571 hudson-jacoco-plugin crashes if jacoco didnt run Issue Type: Bug Assignee: Ognjen Bubalo Components: jacoco Created: 18/Oct/12 3:00 PM Description: Right now the hudson-jacoco-plugin will crash if it is invoked atfter the build is done and the build didn't run jacoco. It should rather gracefully do nothing. The following exception occours: java.io.FileNotFoundException: /jacoco/classes (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.init(FileInputStream.java:137) at org.jacoco.core.analysis.Analyzer.analyzeAll(Analyzer.java:181) at hudson.plugins.jacoco.ExecutionFileLoader.analyzeStructure(ExecutionFileLoader.java:110) at hudson.plugins.jacoco.ExecutionFileLoader.loadBundleCoverage(ExecutionFileLoader.java:116) Project: Jenkins Priority: Major Reporter: Christoph B This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14825) winstone.ClientSocketException: Failed to write to client after upgrade to 1.477
Daniel Beland commented on JENKINS-14825 winstone.ClientSocketException: Failed to write to client after upgrade to 1.477 Same on Windows 2003 with java 1.6.0_29, running as a service. I've upgraded from 1.471 to 1.486 and now it takes many minutes (between 5 and 10) before the page load the first time. Once I get the error in the log file then the page is rendered. The delay is probably due to a default timeout of 5 minutes on the connection. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13395) Still having java.io.StreamCorruptedException with 1.458
Jesse Glick commented on JENKINS-13395 Still having java.io.StreamCorruptedException with 1.458 See: https://github.com/jenkinsci/remoting/pull/6 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10405) Post-receive hook doesn't work
Iristyle commented on JENKINS-10405 Post-receive hook doesnt work I can confirm the same issue with GitHub OAuth enabled. It appears the crux of this issue is when non-standard Jenkins authentication methods are being used. Not even sure you can work around this but some notes in the docs might be helpful. I should note that the solution was the same for me Remove the 'Jenkins (GitHub plugin)' service hook Add a new 'WebHook URL' service hook with a url like https://user:to...@buildserver.com/github-webhook/ I also tried using the above url as the 'Jenkins (GitHub plugin)' url and it did not work. Furthermore, I did check the box to 'Override Hook URL' for the 'GitHub Web Hook' configuration for Jenkins with the same url. Setting that url part worked properly, so it seems that the missing piece to making this work is to update the hook on the GitHub side to handle the credentials properly like 'WebHook URL' does. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10405) Post-receive hook doesn't work
Iristyle edited a comment on JENKINS-10405 Post-receive hook doesnt work I can confirm the same issue with GitHub OAuth enabled. It appears the crux of this issue is when non-standard Jenkins authentication methods are being used. Not even sure you can work around this here but some notes in the docs might be helpful. What I tried to based on above comments was Change the 'Override Hook URL' for the 'GitHub Web Hook' to use `https://user:to...@buildserver.com/github-webhook/` (this only affects new projects) Created a new job, pointed it at a GitHub repo the new style url did persist at GitHub, so that part is working. However, it still didn't work. So I followed the above notes Remove the 'Jenkins (GitHub plugin)' service hook that looks like `https://user:to...@buildserver.com/github-webhook/` Add a new 'WebHook URL' service hook with a url like `https://user:to...@buildserver.com/github-webhook/` It would appear that the missing piece to making this work is to update the hook on the GitHub side to handle the credentials properly like 'WebHook URL' does. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10405) Post-receive hook doesn't work
Iristyle edited a comment on JENKINS-10405 Post-receive hook doesnt work I can confirm the same issue with GitHub OAuth enabled. It appears the crux of this issue is when non-standard Jenkins authentication methods are being used. Not even sure you can work around this here but some notes in the docs might be helpful. What I tried to do, based on above comments was Change the 'Override Hook URL' for the 'GitHub Web Hook' to use https://user:to...@buildserver.com/github-webhook/ (this only affects new projects) Created a new job, pointed it at a GitHub repo the hook was properly registered at GitHub with the updated url style, so at least that part is working. However, it still didn't work when clicking test. So I followed the above recommendations: Remove the 'Jenkins (GitHub plugin)' service hook that looks like https://user:to...@buildserver.com/github-webhook/ Add a new 'WebHook URL' service hook with a url like https://user:to...@buildserver.com/github-webhook/ Note that the user / token is this case is the GitHub user account as well. It would appear that the missing piece to making this work is to update the hook on the GitHub side to handle the credentials properly like 'WebHook URL' does. Note that I also built a custom version of the GitHub-OAuth plugin that fixed the Basic Auth API. They fixed the bug a couple of months ago, but never released an updated plugin, which is a real shame. https://github.com/mocleiri/github-oauth-plugin/commits/master This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15572) Should be able to customize command line executable per slave node
Matt Hauck created JENKINS-15572 Should be able to customize command line executable per slave node Issue Type: New Feature Assignee: Deluan Quintão Components: rtc Created: 18/Oct/12 4:24 PM Description: My jenkins master is running on linux, and I have both mac as well as windows slave nodes. There is a "Tool locations" section that git / perforce and other tools allow customizing the location per-node, and this would be nice for RTC as well. Currently, I am pretty much stuck using "scm" instead of "lscm" since it is the one common name that can be recognized across all three platforms. It would be nice to use the more efficient lscm though. Project: Jenkins Priority: Major Reporter: Matt Hauck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
Richard Mortimer commented on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException For the record I checked in working 1.484 (pre-lazy loading support) and there the HistoryWidget baseList element is a hudson.util.RunList but in broken 1.485 and later it is an instance of hudson.model.RunMap. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8916) Allowing same type of parameter for triggered build more than once seems redundant
Andrew Cockerill commented on JENKINS-8916 Allowing same type of parameter for triggered build more than once seems redundant Hi. I have several Jobs that use multiple 'parameters from properties file' parameters. I would really like to see this functionality put back in. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15562) Support setting the client version
davidstrauss updated JENKINS-15562 Support setting the client version Change By: davidstrauss (18/Oct/12 6:39 PM) Description: Currently,theclientversion(changeablewiththesetVersioncall)defaultstoaPircXstringthatisntveryfriendly.Itwouldbenicetobeabletoincludemoreidentifyinginformationaboutthebotanditsoperators. Itwouldalsobegoodtohavetheversionstringevendefault(whennotsettoanything)tousefulidentifyinginformationabouttheJenkinsinstance. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13754) Error when compiling a plugin against jenkins version 1.463
Kamal Mettananda commented on JENKINS-13754 Error when compiling a plugin against jenkins version 1.463 Workaround of adding deps to POM resolved the problem. Better if someone could update HPI to include this in the POM. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13754) Error when compiling a plugin against jenkins version 1.463
Kamal Mettananda edited a comment on JENKINS-13754 Error when compiling a plugin against jenkins version 1.463 Workaround of adding deps to POM resolved the problem (Maven 2.2.1 Java 6). Better if someone could update HPI to include this in the POM. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-2489) ldap authentication problem in tomcat
Jesse Glick commented on JENKINS-2489 ldap authentication problem in tomcat If 1.289 changed things, JENKINS-2256 or JENKINS-1475 would be related. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-1131) LDAP form validation improvements
Jesse Glick updated JENKINS-1131 LDAP form validation improvements Change By: Jesse Glick (18/Oct/12 8:52 PM) Component/s: ldap Component/s: security This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9771) LDAP group search is not case sensitive, but ACL determination is case sensitive
Jesse Glick updated JENKINS-9771 LDAP group search is not case sensitive, but ACL determination is case sensitive Change By: Jesse Glick (18/Oct/12 8:51 PM) Component/s: ldap Component/s: security This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-5945) CLONE - ClassNotFound in LDAP authentication
Jesse Glick updated JENKINS-5945 CLONE - ClassNotFound in LDAP authentication Change By: Jesse Glick (18/Oct/12 8:52 PM) Component/s: ldap Component/s: security This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13265) Ldap connection failed - jenkins loosing FQDN of ldap server
Jesse Glick updated JENKINS-13265 Ldap connection failed - jenkins loosing FQDN of ldap server Change By: Jesse Glick (18/Oct/12 8:53 PM) Component/s: ldap Component/s: security This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15573) Use of subprocess causes a failure
Kohsuke Kawaguchi created JENKINS-15573 Use of subprocess causes a failure Issue Type: Bug Assignee: Max Spring Components: jenkow-plugin Created: 18/Oct/12 8:52 PM Description: When I created a workflow that involves sub-process, the first task invoked in the subprocess fails to find the proper output. I assume this is because it's not smart enough to associate sub-process execution ID to the parent process execution ID. FATAL: execution 18 doesn't exist org.activiti.engine.ActivitiException: execution 18 doesn't exist at org.activiti.engine.impl.cmd.GetExecutionVariableCmd.execute(GetExecutionVariableCmd.java:52) at org.activiti.engine.impl.interceptor.CommandExecutorImpl.execute(CommandExecutorImpl.java:24) at org.activiti.engine.impl.interceptor.CommandContextInterceptor.execute(CommandContextInterceptor.java:42) at org.activiti.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:33) at org.activiti.engine.impl.RuntimeServiceImpl.getVariable(RuntimeServiceImpl.java:103) at com.cisco.step.jenkins.plugins.jenkow.JenkowRunListener$JenkowExecContext.init(JenkowRunListener.java:58) at com.cisco.step.jenkins.plugins.jenkow.JenkowRunListener$JenkowExecContext.init(JenkowRunListener.java:46) at com.cisco.step.jenkins.plugins.jenkow.JenkowRunListener.onStarted(JenkowRunListener.java:115) at hudson.model.listeners.RunListener.fireStarted(RunListener.java:188) at hudson.model.Run.run(Run.java:1429) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:239) Project: Jenkins Priority: Major Reporter: Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15574) Timeout in Jenkins Task doesn't appear to work
Kohsuke Kawaguchi created JENKINS-15574 Timeout in Jenkins Task doesnt appear to work Issue Type: Bug Assignee: Max Spring Components: jenkow-plugin Created: 18/Oct/12 8:54 PM Description: I've created a small workflow that adds a timeout event to a Jenkins task. I made the timeout trigger in 10sec (PT10S), and the job itself does "sleep 15". Whereas I expected the timeout to fire, it didn't. Project: Jenkins Priority: Major Reporter: Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9443) LDAP security configuration validation is incorrect
Jesse Glick updated JENKINS-9443 LDAP security configuration validation is incorrect Change By: Jesse Glick (18/Oct/12 8:55 PM) Component/s: ldap Component/s: security This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15574) Timeout in Jenkins Task doesn't appear to work
Kohsuke Kawaguchi updated JENKINS-15574 Timeout in Jenkins Task doesnt appear to work Workflow definition Change By: Kohsuke Kawaguchi (18/Oct/12 8:55 PM) Attachment: hello.bpmn This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8465) LDAP get Search access not permitted with that filter error
Jesse Glick updated JENKINS-8465 LDAP get Search access not permitted with that filter error Change By: Jesse Glick (18/Oct/12 8:56 PM) Component/s: ldap Component/s: security This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12920) LDAP autentication has incorrect credentials for user
Jesse Glick updated JENKINS-12920 LDAP autentication has incorrect credentials for user Change By: Jesse Glick (18/Oct/12 8:56 PM) Component/s: ldap Component/s: security This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14520) LDAP Plugin should support StartTLS extension
Jesse Glick updated JENKINS-14520 LDAP Plugin should support StartTLS extension Change By: Jesse Glick (18/Oct/12 8:57 PM) Component/s: ldap Component/s: security This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9771) LDAP group search is not case sensitive, but ACL determination is case sensitive
Jesse Glick resolved JENKINS-9771 as Duplicate LDAP group search is not case sensitive, but ACL determination is case sensitive Change By: Jesse Glick (18/Oct/12 9:00 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15575) No Post-Build Actions Are Ever Run
Greg horvath created JENKINS-15575 No Post-Build Actions Are Ever Run Issue Type: Bug Assignee: Nicolas De Loof Components: build-flow Created: 18/Oct/12 10:11 PM Description: I can save post build actions, but they are never run. This closed ticket says that it was fixed in the current release, but I don't see that being the case. https://issues.jenkins-ci.org/browse/JENKINS-14411 Please fix so that post-build actions can be run after the flow completes. Environment: Jenkins 1.486 / CentOS Project: Jenkins Priority: Major Reporter: Greg horvath This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14901) Emulator start failed on Ubuntu (SDK 20.0.3)
David Tanner commented on JENKINS-14901 Emulator start failed on Ubuntu (SDK 20.0.3) I also have this issue and was able to get the plugin to recognize the launched plugin by renaming emulator-arm to emulator This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15466) Fatal Error No Class Definition found for Kernel32
Pei-Tang Huang commented on JENKINS-15466 Fatal Error No Class Definition found for Kernel32 I got similar exception while wiping out remote workspace on Jenkins 1.486: Status Code: 500 Exception: remote file operation failed: D:\AppData\Jenkins\workspace\tac at hudson.remoting.Channel@5683bdec:Analysis 1 Stacktrace: hudson.util.IOException2: remote file operation failed: D:\AppData\Jenkins\workspace\tac at hudson.remoting.Channel@5683bdec:Analysis 1 at hudson.FilePath.act(FilePath.java:847) at hudson.FilePath.act(FilePath.java:824) at hudson.FilePath.deleteRecursive(FilePath.java:980) at hudson.model.AbstractProject.doDoWipeOutWorkspace(AbstractProject.java:1901) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at
[JIRA] (JENKINS-13395) Still having java.io.StreamCorruptedException with 1.458
Kristia Rosenvold commented on JENKINS-13395 Still having java.io.StreamCorruptedException with 1.458 I closed the pull request because it was obviously not going to work that way. I re-read our discussion on the pull request and I think I understand that you're fine with externalizing the "start" method from the construction logic ? All clients would still have to be updated to call "start" (or we could shudder do it lazily), since there is to my best knowledge no safe way to start a thread referencing "this" in a constructor. I can rework the patch once you confirm you think this is ok This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
