[JIRA] (JENKINS-9913) Concurrent builds getting batched/nodes not getting released when jobs are completed
Sergey Smirnov updated JENKINS-9913 Concurrent builds getting batched/nodes not getting released when jobs are completed Change By: Sergey Smirnov (19/Oct/12 6:20 AM) Attachment: jenkins2.jpeg Attachment: jenkins1.jpeg 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
Sergey Smirnov commented on JENKINS-9913 Concurrent builds getting batched/nodes not getting released when jobs are completed I attached to screenshot to explain again what's happen. Jobs 537, 538, 539 have finished as you can see on second screenshot. But executors is still busy as you can see on first one. 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-15577) Lazy loading breaks histories in MultiJob plugins
Arnaud Héritier created JENKINS-15577 Lazy loading breaks histories in MultiJob plugins Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2012-10-19 at 9.04.17 AM.png Components: core, jenkins-multijob-plugin Created: 19/Oct/12 7:08 AM Description: Old builds are greyed and marked as "not run" whereas they were Environment: 1.486 + Multijob 1.5 Project: Jenkins Priority: Major Reporter: Arnaud Héritier 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-15577) Lazy loading breaks history of children jobs in MultiJob plugins
Arnaud Héritier updated JENKINS-15577 Lazy loading breaks history of children jobs in MultiJob plugins Change By: Arnaud Héritier (19/Oct/12 7:18 AM) Summary: Lazyloadingbreaks histories historyofchildrenjobs inMultiJobplugins 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-15577) Lazy loading breaks history of children jobs in MultiJob plugins
Arnaud Héritier deleted JENKINS-15577 Lazy loading breaks history of children jobs in MultiJob plugins 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
Michael Clarke commented on JENKINS-13032 Updating cvs plugin to version 2.0 causes java.lang.RuntimeException: CVS authentication failure while running rlog command See https://github.com/jenkinsci/cvsclient/blob/master/src/main/java/org/netbeans/lib/cvsclient/Client.java#L361 This is the method that's causing the error you're seeing whilst it's trying to do it open a connection to the server, with a timeout of 1 minute before failing the connection. If the server fails to accept the connection within this time then the exception you see is thrown. This method doesn't issue any CVS commands, only looks for a network port connection so would be impacted by proxy servers and/or firewall restrictions. Do you have either of these between your Jenkins server and your CVS server? Note: Pinging your server only shows the network stack is responding, CVS Server sits ontop of this and could be failing to respond whilst the ping command shows the server as being available. 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
commented on JENKINS-13032
Updating cvs plugin to version 2.0 causes java.lang.RuntimeException: CVS authentication failure while running rlog command
Yes, we have a proxy. I setted up Jenkins to use this proxy in the plugin management, but I added the CVS server hostname in exception list ("No proxy host"). Is the plugin using those settings?
Moreover, we have a strange behavior. When we got this error, if we restart the application server, CVS server is reachable.
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-14953) Exclusion plugin sometimes reports a resource as locked when it is not. Jobs hang as a result.
Anthony Roux commented on JENKINS-14953 Exclusion plugin sometimes reports a resource as locked when it is not. Jobs hang as a result. Development has been done I will release as soon as I have time. 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-12205) Test result trend not displayed in matrix project configuration top page
sa bu commented on JENKINS-12205 Test result trend not displayed in matrix project configuration top page hello, I have exactly the same problem. Do you have a solution? 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-12205) Test result trend not displayed in matrix project configuration top page
sa bu edited a comment on JENKINS-12205 Test result trend not displayed in matrix project configuration top page hello, I have exactly the same problem. Do you have a solution? I use Jenkins ver. 1.485 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-14057) With Active Directory Plugin, the user/group validation in authorization strategy of configuration screen fails
William Roberts commented on JENKINS-14057 With Active Directory Plugin, the user/group validation in authorization strategy of configuration screen fails See also Jenkins-12619 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-15578) hudson.security.AccessDeniedException2: anonymous is missing the Administer permission
Craig Newell created JENKINS-15578 hudson.security.AccessDeniedException2: anonymous is missing the Administer permission Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: ios-device-connector Created: 19/Oct/12 9:38 AM Description: I have my Jenkins installation configured to require LDAP logins and only certain users are administrators and the rest just have read only rights. When restarting Jenkins after installing the ios-device-connector plugin, all my slaves fail to connect with the following: ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins. hudson.security.AccessDeniedException2: anonymous is missing the Administer permission at hudson.security.ACL.checkPermission(ACL.java:54) at hudson.model.Node.checkPermission(Node.java:393) at org.jenkinsci.plugins.ios.connector.iOSDeviceList.update(iOSDeviceList.java:91) at org.jenkinsci.plugins.ios.connector.ComputerListenerImpl.onOnline(ComputerListenerImpl.java:21) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:396) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:317) at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:454) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:293) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:200) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) If I allow all users administrator access, then the slaves reconnect correctly and I can see the iOS device status. Environment: Jenkins 1.486 on Linux x86 with Mac OS X 10.8.2 slaves Project: Jenkins Priority: Blocker Reporter: Craig Newell 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-15580) svn export instead of svn checkout in jenkins
amit anand created JENKINS-15580 svn export instead of svn checkout in jenkins Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: svn-release-mgr Created: 19/Oct/12 9:52 AM Description: I need to use svn export instead of svn checkout in jenkins Due Date: 21/Oct/12 12:00 AM Environment: Please let me know if we have any option in jenkins for export Project: Jenkins Priority: Blocker Reporter: amit anand 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-14752) SCM Polling / Max # of concurrent polling = 1 hangs github polling
Sascha Vogt commented on JENKINS-14752 SCM Polling / Max # of concurrent polling = 1 hangs github polling Same here with the following env: git version: 1.7.2.5 Debian: 6.0.5 Java: Sun/Oracle JDK 1.6.0_26 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 commented on JENKINS-13032 Updating cvs plugin to version 2.0 causes java.lang.RuntimeException: CVS authentication failure while running rlog command I'm using GlassFish App Server v3.1.2.2. The issue re-occurs from time to time but when it reoccurs, the only solution we've found for the moment is to stop et start GlassFish. There is no automatic recover. 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-12377) Jenkins fitnesse build aborts after HTTP Timeout is exceeded, but tests continue to run
Mike Guiney commented on JENKINS-12377 Jenkins fitnesse build aborts after HTTP Timeout is exceeded, but tests continue to run Hi, A closer look at this seems to be an issue with the fitnesse instance not handling multiple clients running custom suites in parallel. We use custom tags in fitnesse to run a subset of tests as part of a number of smoke test jobs. Our Fitnesse instance doesn't respond well to FitServer.exe which is left hanging in the wind. still investigating... Mike 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-15581) Error on build other projects (post build actions)
James Walker created JENKINS-15581 Error on build other projects (post build actions) Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: Jenkins_error.txt Components: postbuild-task Created: 19/Oct/12 11:19 AM Description: When we create a new job and select 'build other projects' in the post build actions we no longer see the three radio button options which are 'Trigger only if build succeeds', 'Trigger even if the build is unstable' and 'Trigger even if the build fails'. We also get an error in the logs, which you can see attached. We think it might have something to do with the Parameterized Trigger plugin that we installed. Since it seem to break after we installed it. Removing the plugin doesn't seem to help either. Environment: Solaris 10 Project: Jenkins Priority: Major Reporter: James Walker 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-12093) Allow per-project category throttling on the same job
Sebastian Schuberth
commented on JENKINS-12093
Allow per-project category throttling on the same job
To solve the UI nightmare somewhat it would be nice if the "Multi-Project Throttle Category" checkboxes were hidden / disabled if "Throttle this project alone" is selected.
More general, what about a UI like this ("()" indicating radio buttons, "[]" indicating checkboxes):
Apply thread limits from () project only () project, then categories
Maximum total concurrent builds _
Maximum concurrent builds per node_
Throttle category membership [] category name 1 [] category name 2 ...
Similar to what I suggested in the beginning, the last line should only be display if the "project, then categories" radio button is selected.
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-15582) Slave Setup Plugin fails with an exception
S G created JENKINS-15582 Slave Setup Plugin fails with an exception Issue Type: Bug Assignee: Unassigned Components: plugin Created: 19/Oct/12 11:22 AM Project: Jenkins Priority: Major Reporter: S G 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-15582) Slave Setup Plugin fails with an exception
S G
commented on JENKINS-15582
Slave Setup Plugin fails with an exception
Am lauching slave through SSH. After successful authentication the launch fails with below exception
Jenkins Version - 1.424.6
Slave - Redhat 5.5
Slave Launch method - "Launch slave via execution of command on the master"
Exception
-
debug1: channel 0: new client-session
debug1: Entering interactive session.
debug1: Sending environment.
debug1: Sending command: java -jar /opt/installers/slave.jar
===JENKINS REMOTING CAPACITY===Slave.jar version: ${build.version}
This is a Unix slave
just before slave MyClient Group - MyClient Environment Setups gets online ...
ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins
java.lang.NoClassDefFoundError: org/jenkinsci/plugins/slave_setup/SetupConfig
at org.jenkinsci.plugins.slave_setup.ComputerListenerImpl.preOnline(ComputerListenerImpl.java:32)
at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:353)
at hudson.slaves.CommandLauncher.launch(CommandLauncher.java:121)
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:198)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
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
Michael Clarke commented on JENKINS-13032 Updating cvs plugin to version 2.0 causes java.lang.RuntimeException: CVS authentication failure while running rlog command Next time you have the failure, could you go to /threadDump on your Jenkins host (e.g. http://localhost:8080/threadDump) before and after your restart so I can see if there's any rogue threads hanging around. 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-14900) Copying from workspace drops files matching Ant's default excludes
Dave Hunt commented on JENKINS-14900 Copying from workspace drops files matching Ants default excludes Pull request with failing test that demonstrates this issue is here: https://github.com/jenkinsci/copyartifact-plugin/pull/12 This is preventing us from upgrading Jenkins past version 1.455 (March 2012) 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 are able to work around the problem by adding: ClientAliveInterval 60 to /etc/ssh/sshd_config on the Jenkins host 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-15584) [xunit] processing CppUnit-1.12.1 failed
Julie Nicolas created JENKINS-15584 [xunit] processing CppUnit-1.12.1 failed Issue Type: Bug Assignee: Gregory Boissinot Components: xunit Created: 19/Oct/12 2:12 PM Description: My jobs failed when processing CppUnit with this error : ERROR: Publisher org.jenkinsci.plugins.xunit.XUnitPublisher aborted due to exception hudson.util.IOException2: remote file operation failed: /var/jenkins/workspace/nameOfMyJob at hudson.remoting.Channel@cb61b:runner-rh4u8 at hudson.FilePath.act(FilePath.java:838) at hudson.FilePath.act(FilePath.java:824) at org.jenkinsci.plugins.xunit.XUnitPublisher.performTests(XUnitPublisher.java:170) at org.jenkinsci.plugins.xunit.XUnitPublisher.performXUnit(XUnitPublisher.java:115) at org.jenkinsci.plugins.xunit.XUnitPublisher.perform(XUnitPublisher.java:92) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639) at hudson.model.Run.execute(Run.java:1513) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: java.io.IOException: Remote call on runner-rh4u8 failed at hudson.remoting.Channel.call(Channel.java:672) at hudson.FilePath.act(FilePath.java:831) ... 13 more Caused by: java.lang.ClassFormatError: Failed to load com.thalesgroup.dtkit.junit.CppUnit at hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:154) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:131) at java.lang.ClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClassInternal(Unknown Source) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Unknown Source) at hudson.remoting.MultiClassLoaderSerializer$Input.resolveClass(MultiClassLoaderSerializer.java:113) at java.io.ObjectInputStream.readNonProxyDesc(Unknown Source) at java.io.ObjectInputStream.readClassDesc(Unknown Source) at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.defaultReadFields(Unknown Source) at java.io.ObjectInputStream.readSerialData(Unknown Source) at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.defaultReadFields(Unknown Source) at java.io.ObjectInputStream.readSerialData(Unknown Source) at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.defaultReadFields(Unknown Source) at java.io.ObjectInputStream.readSerialData(Unknown Source) at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.readObject(Unknown Source) at hudson.remoting.UserRequest.deserialize(UserRequest.java:182) at hudson.remoting.UserRequest.perform(UserRequest.java:98) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.UnsupportedClassVersionError: Bad version number in .class file at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(Unknown Source) at
[JIRA] (JENKINS-15419) TAP published results hide JUnit published results
Bruno P. Kinoshita closed JENKINS-15419 as Fixed TAP published results hide JUnit published results Fixed in 1.6 Change By: Bruno P. Kinoshita (19/Oct/12 3:57 PM) 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-15497) Display link to download TAP attachment
Bruno P. Kinoshita closed JENKINS-15497 as Fixed Display link to download TAP attachment Fixed in 1.6 Change By: Bruno P. Kinoshita (19/Oct/12 3:57 PM) 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-14900) Copying from workspace drops files matching Ant's default excludes
Alan Harder assigned JENKINS-14900 to Unassigned Copying from workspace drops files matching Ants default excludes sorry, haven't worked on jenkins in a couple years Change By: Alan Harder (19/Oct/12 4:17 PM) Assignee: AlanHarder 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-14900) Copying from workspace drops files matching Ant's default excludes
Dave Hunt assigned JENKINS-14900 to Jesse Glick Copying from workspace drops files matching Ants default excludes Apologies if this is the wrong person to assign to - I was going by recent commits to this plugin. Change By: Dave Hunt (19/Oct/12 4:30 PM) Assignee: JesseGlick 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-11280) Downstream project name is not accepting env variable/build parameters
Tom Canova commented on JENKINS-11280 Downstream project name is not accepting env variable/build parameters Please fix this bug - I need this fixed so I can fully use parameters in my jobs and not have to hardcode variable stuff directly in parameterized trigger fields. 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-9584) Sometimes after Jenkins restart platform labels are not available
markewaite commented on JENKINS-9584 Sometimes after Jenkins restart platform labels are not available I've seen a similar situation on my Debian installation. After restart, the slave node label is visible in the configuration, but the jobs will not schedule on that slave node until I save the (unchanged) configuration of the slave node. 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-14550) Checksum mismatch while updating with Subversion Plugin 1.42
David Humeniuk commented on JENKINS-14550 Checksum mismatch while updating with Subversion Plugin 1.42 This issue is included in the changelog for 1.43, but this issue hasn't been updated to reflect 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-14629) plugin don't fail the build when checkout failed
David Humeniuk commented on JENKINS-14629 plugin dont fail the build when checkout failed This issue is included in the changelog for 1.43, but this issue hasn't been updated to reflect 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-13790) Subversion externals fail
tq rst commented on JENKINS-13790 Subversion externals fail Seeing the same error in my build logs for 1.486, but the error doesn't appear to be fatal. The rest of the repo checks out properly and the build works fine. 14:43:45 AssertionError: appears to be using unpatched svnkit at file:/tmp/hudson-remoting4395012546022522440/org/tmatesoft/svn/core/wc/SVNEvent.class This is with svn 1.7. 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-15584) [xunit] processing CppUnit-1.12.1 failed
Gregory Boissinot commented on JENKINS-15584 [xunit] processing CppUnit-1.12.1 failed Maybe it is Java version issue. The plugin is supposed to work with Java 6. Please could give me your Java version and provider? 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-15584) [xunit] processing CppUnit-1.12.1 failed
Gregory Boissinot started work on JENKINS-15584 [xunit] processing CppUnit-1.12.1 failed Change By: Gregory Boissinot (19/Oct/12 7:02 PM) Status: Open InProgress 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-15585) If you have a windows master, linux slave, the grails plugin tries to run grails as using windows slashes and the bat file as executable
Michael Chmielewski created JENKINS-15585 If you have a windows master, linux slave, the grails plugin tries to run grails as using windows slashes and the bat file as executable Issue Type: Bug Affects Versions: current Assignee: jeffg2one Components: grails Created: 19/Oct/12 7:42 PM Description: I am installing grails 2.0.4 using the mirrors. The installation goes correctly, but when my build tries to run grails, I see the following: Unpacking http://dist.springframework.org.s3.amazonaws.com/release/GRAILS/grails-2.0.4.zip to /home/jenkins/tools/Grails/Grails_2.0.4 on Deuterium FATAL: \home\jenkins\tools\Grails\Grails_2.0.4\bin\grails.bat doesn't exist Build step 'Build With Grails' marked build as failure The path is right, but the slashes are wrong, and it shouldn't use grails.bat Environment: Windows Server 2003 master CentOS 6.3 x64 slave Project: Jenkins Labels: plugin windows master linux slave grails Priority: Major Reporter: Michael Chmielewski 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-15419) TAP published results hide JUnit published results
Joe Hansche commented on JENKINS-15419 TAP published results hide JUnit published results How funny, I was just noticing this and about to file an issue, but I see it's already been fixed. Has 1.6 already been published to the update center? I just installed 1.5 a few hours ago. 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-12575) Add option to sort JUNIT tests by date (currently ordered alphabetically)
Alex Okrushko updated JENKINS-12575 Add option to sort JUNIT tests by date (currently ordered alphabetically) Indeed alphabetical order is very frustrating (refer to test_results.png), specially where tests are run in scenarios (in brackets) Change By: Alex Okrushko (19/Oct/12 8:43 PM) Attachment: test_results.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-15419) TAP published results hide JUnit published results
Bruno P. Kinoshita commented on JENKINS-15419 TAP published results hide JUnit published results Hi Joe, really funny, especially since I didn't imagine so many people would be using JUnit and TAP in the same project The synchronization should take a while for 1.6. Try again in few hours. I think it gets synchronized every four hours or so. Thanks. 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-15540) Update logging levels in LogRotator - hudson.tasks.LogRotator perform
Wade C commented on JENKINS-15540 Update logging levels in LogRotator - hudson.tasks.LogRotator perform https://github.com/jenkinsci/jenkins/pull/592 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-13361) Build IPA causes dSYM.zip to include absolute paths
Evan Doll commented on JENKINS-13361 Build IPA causes dSYM.zip to include absolute paths This is causing some problems when we upload our zipped .dSYM to our crash reporting service. I've modified it locally to use "ditto -c -k --keepParent -rsrc" rather than zip, seems to work fine. 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-13361) Build IPA causes dSYM.zip to include absolute paths
Evan Doll commented on JENKINS-13361 Build IPA causes dSYM.zip to include absolute paths Added a pull request with a fix: https://github.com/jenkinsci/xcode-plugin/pull/13 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
