[JIRA] [pmd] (JENKINS-24873) Wrong number of new warnings
Sergey Ryazantsev commented on JENKINS-24873 Wrong number of new warnings Thank you, Ulli! I've tested the 3.39-SNAPSHOT version from your CI server and the problem hasn't reproduced. I'm looking forward to plugin release! 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 -- 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-25144) Basic Authentication in combination with Session is broken
uncletall commented on JENKINS-25144 Basic Authentication in combination with Session is broken Failing to fix this, there should be at least a WARNING on the main page telling people not to install the latest version if the are running behind a reverse proxy. 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 -- 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] [slave-status] (JENKINS-25329) java.lang.NoClassDefFoundError: hudson/slaves/SlaveComputer
Xiao Jin Zhao created JENKINS-25329 java.lang.NoClassDefFoundError: hudson/slaves/SlaveComputer Issue Type: Bug Assignee: Unassigned Components: slave-status Created: 28/Oct/14 6:43 AM Description: Any time when start a task to execute installation on Windows 2012 slave, a fatal failure returned as below, however the slave node do connect already: FATAL: Remote call on ... failed java.io.IOException: Remote call on ... failed at hudson.remoting.Channel.call(Channel.java:748) at hudson.Launcher$RemoteLauncher.kill(Launcher.java:918) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:558) at hudson.model.Run.execute(Run.java:1740) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:234) Caused by: java.lang.NoClassDefFoundError: hudson/slaves/SlaveComputer at hudson.util.ProcessTree.getKillers(ProcessTree.java:151) at hudson.util.ProcessTree$OSProcess.killByKiller(ProcessTree.java:212) at hudson.util.ProcessTree$Windows$1.killRecursively(ProcessTree.java:404) at hudson.util.ProcessTree$Windows.killAll(ProcessTree.java:461) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:930) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:921) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314) at java.util.concurrent.FutureTask.run(FutureTask.java:149) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:906) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:929) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Thread.java:738) Environment: Jenkins 1.575 Project: Jenkins Priority: Blocker Reporter: Xiao Jin Zhao 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 -- 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-25144) Basic Authentication in combination with Session is broken
Daniel Beck commented on JENKINS-25144 Basic Authentication in combination with Session is broken Please have a look at this I'm sure he'll get right to it after taking care of the other 385 issues assigned to him. (IOW, it's usually more effective to bring issues to someone's attention via other channels.) WARNING on the main page telling people not to install the latest version You can vote on the changelog ("Community rating") and tell people about this bug. TBH I think you're overestimating the impact of this issue. Isn't it easily circumvented by sending User/Password with every request instead of relying on Session ID? 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 -- 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] [xcode] (JENKINS-20916) Code Sign error: No matching provisioning profile found
Tom Hicks commented on JENKINS-20916 Code Sign error: No matching provisioning profile found "restore keychains as defined in global configuration" doesn't work for me I had to add a shell task 'security delete-keychain "jenkins-$JOB_NAME" || :' to delete the keychain if it existed before. I also added an "Import developer profile" task and put my *.developerprofile file in the credentials system. I still couldn't sign and a shell task would show no code signing keys present, because the keys aren't imported into the login.keychain keychain. You need to also expand "Code signing OS X keychain options", check "Unlock Keychain?" and fill in the path to the keychain file ie "${HOME}/Library/Keychains/jenkins-${JOB_NAME}" and the password you used for the *.developerprofile file as the Keychain password. 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 -- 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] [ci-game] (JENKINS-24478) Publisher hudson.plugins.cigame.GamePublisher aborted due to exception NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTe
Dirk Olmes commented on JENKINS-24478 Publisher hudson.plugins.cigame.GamePublisher aborted due to exception NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction I can confirm that the snapthos link you provided above works. Please release a fixed version. 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 -- 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-25144) Basic Authentication in combination with Session is broken
Christof Schoell commented on JENKINS-25144 Basic Authentication in combination with Session is broken A Session is created automatically and the User/Password is sent with every request through the proxy. That's when the problem occurs. Without any Session Id (which you would have to filter out inside the proxy) the functionality of jenkins is reduced as well... 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 -- 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-25270) Add option to disable configuration confirmation dialog
Gunnar Strand commented on JENKINS-25270 Add option to disable configuration confirmation dialog Thanks for the tip. Unfortunately CVS is already disabled in our installation. 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 -- 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] (JENKINS-25330) Folders should offer to use a hash for workspace path (like matrix does)
Félix Belzunce Arcos created JENKINS-25330 Folders should offer to use a hash for workspace path (like matrix does) Issue Type: Improvement Assignee: Nicolas De Loof Components: cloudbees-folder Created: 28/Oct/14 8:08 AM Description: When jobs are organized with lots of nested folders, the resulting workspace path can be long and will hit the windows 255 character max length (yes, we are in XXIth century and still suffer such issues) Matrix job offer an option to use a hash for workspace path as a workaround, folder could offer a comparable solution. Project: Jenkins Priority: Minor Reporter: Félix Belzunce Arcos 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 -- 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] [hp-application-automation-tools-plugin] (JENKINS-25331) Custom code is not executing when running API tests using HP Application Automation Plug-in
Venkata Praveen B created JENKINS-25331 Custom code is not executing when running API tests using HP Application Automation Plug-in Issue Type: Bug Assignee: Ofir Shaked Attachments: UFT API Test SS1.jpg, UFT API Test SS2.jpg Components: hp-application-automation-tools-plugin Created: 28/Oct/14 8:12 AM Description: We developed API tests using HP UFT v12.01 and added Custom Code activity to perform certain customized functionality (Configuring UFT settings during run-time, create MS excel instance, writing data to excel file, creating folder etc.). The custom code is written in C#.net language. When executing the API test from UFT IDE then the custom code is executing and performing intended operations. But when the same test is executed through Jenkins using HP Application Automation tools plug-in, we observed that the code is not being executed and not performing any intended operations. Screenshots attached for reference... The Console Output showing the particular custom code is executed and completed but we are not seeing any folder created/data written to excel file etc. Pls let me know if you need further information...Thank you... Environment: Jenkins v1.584 HP Application Automation Tools 3.0.6 plug-in installed Using Windows 7 OS with IE9 browser Using UFT v12.01 tool with HP ALM 11.52 Project: Jenkins Labels: plugin jenkins Priority: Major Reporter: Venkata Praveen 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 -- 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-18032) Delete Project link fails with 403 Exception: No valid crumb was included in the request
Thomas Pummer commented on JENKINS-18032 Delete Project link fails with 403 Exception: No valid crumb was included in the request Got the same problem in 1.581 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 -- 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-18032) Delete Project link fails with 403 Exception: No valid crumb was included in the request
Thomas Pummer edited a comment on JENKINS-18032 Delete Project link fails with 403 Exception: No valid crumb was included in the request Got the same problem in 1.581, workaround is still valid 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 -- 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-18032) Delete Project link fails with 403 Exception: No valid crumb was included in the request
Thomas Pummer reopened JENKINS-18032 Delete Project link fails with 403 Exception: No valid crumb was included in the request Got the same problem in 1.581, workaround is still valid Change By: Thomas Pummer (28/Oct/14 8:34 AM) Resolution: Fixed Status: Resolved 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 -- 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-25144) Basic Authentication in combination with Session is broken
uncletall commented on JENKINS-25144 Basic Authentication in combination with Session is broken This is my server config. Is there anything I can change to workaround this bug? I am not doing anything with a Session ID, at least not that I am aware of. Location "/" AuthBasicProvider ldap AuthType Basic AuthName "example.com" AuthzLDAPAuthoritative off AuthLDAPURL "ldap://example.com/ou=users,dc=example,dc=com?uid?one" Require valid-user RequestHeader set REMOTE_USER %{REMOTE_USER}s /Location AllowEncodedSlashes On RewriteEngine On Proxy * Order deny,allow Allow from all /Proxy Jenkins Location /ci ProxyPass http://192.168.1.2:8080/ci/ ProxyPassReverse / Order deny,allow Allow from all /Location Header edit Location ^http://example.com/ci/ https://example.com/ci/ Gerrit ProxyPass /r/ http://192.168.1.1:8081/r/ nocanon Wiki ProxyPass /wiki/ https://192.168.1.3/wiki/ ProxyPassReverse /wiki/ https://192.168.1.3/wiki/ ProxyPass /w/ https://192.168.1.3/w/ ProxyPassReverse /w/ https://192.168.1.3/w/ 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 -- 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-25144) Basic Authentication in combination with Session is broken
Christof Schoell commented on JENKINS-25144 Basic Authentication in combination with Session is broken Nope you can't really do anything about this by config. You would have to remove the JSESSIONID set by Jenkins (or tomcat really) from the cookie so you do not have a session any more. On the other hand this would remove any functionality from Jenkins which requires a session (e.g. icon sizes in the summary view) 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 -- 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-25144) Basic Authentication in combination with Session is broken
Christof Schoell edited a comment on JENKINS-25144 Basic Authentication in combination with Session is broken You would have to remove the JSESSIONID set by Jenkins (or tomcat really) from the cookie header so you do not have a session any more. This isn't really practicable but I guess it could be possible... On the other hand this would remove any functionality from Jenkins which requires a session (e.g. icon sizes in the summary view) 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 -- 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] [perforce-plugin] (JENKINS-25332) Workspace changes does not trigger a full sync
Morne Joubert created JENKINS-25332 Workspace changes does not trigger a full sync Issue Type: Bug Assignee: Rob Petti Components: perforce-plugin Created: 28/Oct/14 9:38 AM Description: If a job's Jenkins workspace changes then a full sync is not done. Easy to replicate. Create a job with a custom workspace e.g: /workspace/test/ Do a sync and build Check in a single file Change custom workspace to /workspace/test2 Run job. New local workspace has only the single change. On a jenkins workspace change a full sync needs to happen to make sure the p4 have lists and local files are actually correct Project: Jenkins Priority: Critical Reporter: Morne Joubert 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 -- 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] [perforce-plugin] (JENKINS-25332) Workspace changes does not trigger a full sync
Morne Joubert updated JENKINS-25332 Workspace changes does not trigger a full sync Change By: Morne Joubert (28/Oct/14 9:38 AM) Priority: Critical Major 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 -- 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] [security] (JENKINS-25333) Jenkins 1.586 not starting up using Java8
Max Wahler created JENKINS-25333 Jenkins 1.586 not starting up using Java8 Issue Type: Bug Assignee: Unassigned Components: security Created: 28/Oct/14 9:44 AM Description: Using Java8, Jenkins doesn't start with the following message: SCHWERWIEGEND: Container startup failed java.io.IOException: Failed to start a listener: winstone.HttpsConnectorFactory at winstone.Launcher.spawnListener(Launcher.java:209) at winstone.Launcher.init(Launcher.java:149) at winstone.Launcher.main(Launcher.java:354) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at Main._main(Main.java:293) at Main.main(Main.java:98) Caused by: java.lang.NoClassDefFoundError: sun/security/x509/CertAndKeyGen at winstone.HttpsConnectorFactory.start(HttpsConnectorFactory.java:101) at winstone.Launcher.spawnListener(Launcher.java:207) ... 8 more Caused by: java.lang.ClassNotFoundException: sun.security.x509.CertAndKeyGen at java.net.URLClassLoader$1.run(URLClassLoader.java:372) at java.net.URLClassLoader$1.run(URLClassLoader.java:361) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:360) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ... 10 more After switching back to Oracle Java 7, it works without problems. Environment: Debian 7 Wheezy x86-64, Oracle Java 8, Jenkins 1.586 Project: Jenkins Labels: jenkins exception Priority: Critical Reporter: Max Wahler 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 -- 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] [jacoco] (JENKINS-25334) Percentage link does not work in non-default views
Catalin Luta created JENKINS-25334 Percentage link does not work in non-default views Issue Type: Bug Assignee: Ognjen Bubalo Attachments: DefaultViewLink.jpg, NormalViewLink.png Components: jacoco Created: 28/Oct/14 10:01 AM Description: The quick link present on the Jacoco column does not seem to work for non default views. The view path is apparently duplicated in the a href link, thus pointing to an invalid path (please see the attached image NormalViewLink.png; I've also provided the default link in DefaultViewLink.jpg). Let me know if I can provide further details. Environment: Jenkins 1.580, Jacoco plugin version 1.0.16, Ubuntu 14.04.1 LTS Project: Jenkins Priority: Minor Reporter: Catalin Luta 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 -- 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] [jacoco] (JENKINS-25334) Percentage link does not work in non-default views
Catalin Luta updated JENKINS-25334 Percentage link does not work in non-default views Change By: Catalin Luta (28/Oct/14 10:03 AM) Description: ThequicklinkpresentontheJacococolumndoesnotseemtoworkfornondefaultviews.Theviewpathisapparentlyduplicatedintheahreflink,thuspointingtoaninvalidpath(pleaseseetheattachedimage * NormalViewLink.png * ;Ivealsoprovidedthedefaultlinkin * DefaultViewLink.jpg * ).LetmeknowifIcanprovidefurtherdetails. 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 -- 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-751) hudson.tasks.junit.AbortException thrown on some maven2 projects
Frank Mueller reopened JENKINS-751 hudson.tasks.junit.AbortException thrown on some maven2 projects Problem seems to be back in 1.565.3 Started a multi module maven build with parameter -Dmaven.test.failure.ignore=true Jasmine tests will not be executed but jenkins still tries to get the test results. [INFO] --- jasmine-maven-plugin:1.3.1.4:test (default) @ lh-ress-ui --- [INFO] Skipping Jasmine Specs [JENKINS] Zeichne Testergebnisse auf hudson.AbortException: Test reports were found but none of them are new. Did tests run? For example, /home/jenkinslocal/jenkins-jobs/workspace/lufthansa-reactor-master-SNAPSHOT-NEW/lufthansa-ress-ui/target/jasmine/TEST-jasmine.xml is 44 Jahre old at hudson.tasks.junit.TestResult.parse(TestResult.java:213) at hudson.maven.reporters.SurefireArchiver.postExecute(SurefireArchiver.java:148) at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoEnded(Maven3Builder.java:628) at hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:610) at hudson.maven.Maven3Builder$JenkinsEventSpy.onEvent(Maven3Builder.java:306) at org.apache.maven.eventspy.internal.EventSpyDispatcher.onEvent(EventSpyDispatcher.java:108) at org.apache.maven.eventspy.internal.EventSpyExecutionListener.mojoSucceeded(EventSpyExecutionListener.java:131) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:87) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:227) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152) at org.jvnet.hudson.maven3.launcher.Maven31Launcher.main(Maven31Launcher.java:132) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238) at jenkins.maven3.agent.Maven31Main.launch(Maven31Main.java:181) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.maven.Maven3Builder.call(Maven3Builder.java:134) at hudson.maven.Maven3Builder.call(Maven3Builder.java:69) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) [INFO] Change By: Frank Mueller (28/Oct/14 10:20 AM) Resolution: Fixed Status: Closed Reopened
[JIRA] [p4] (JENKINS-25335) Support for variables when specifying stream
Morne Joubert created JENKINS-25335 Support for variables when specifying stream Issue Type: Bug Assignee: Unassigned Components: p4 Created: 28/Oct/14 10:24 AM Description: It doesn't look as if i can specify a variable for the P4 stream e.g. ${perforceStream} the value seems to be only available as a pull down list on the GUI Project: Jenkins Priority: Minor Reporter: Morne Joubert 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 -- 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] (JENKINS-24624) Support for shared workspaces
Morne Joubert commented on JENKINS-24624 Support for shared workspaces I have configure the project to behave as follows _MA_SW_ci_tools${EXECUTOR_NUMBER}jenkins_p4${SITE}-${NODE_NAME} where _MA_SW_ci_tools is a reference to a unique P4 stream. It seems to work 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 -- 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-25325) Update to Jenkins 1.565.3 causes Java 5 Maven builds to fail
Daniel Beck resolved JENKINS-25325 as Duplicate Update to Jenkins 1.565.3 causes Java 5 Maven builds to fail Duplicates JENKINS-25272. Change By: Daniel Beck (28/Oct/14 10:37 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 -- 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] [android-emulator] (JENKINS-25336) ABI name parsing is broken
Christopher Orr created JENKINS-25336 ABI name parsing is broken Issue Type: Bug Assignee: Christopher Orr Components: android-emulator Created: 28/Oct/14 11:14 AM Description: Creating an emulator without an ABI specified tries to inform the user which ABIs are available for this platform. Currently with SDK Tools 23.0.5, I'm getting this output, with "default/" prepended to each name: android /home/chris/android/sdk/tools/android create avd -f -a -s WXGA800 -n hudson_fr-CA_240_WXGA800_android-15 -t android-15 There is more than one system image defined for platform 'android-15'. Pick an image to use and set it in the 'Target ABI' config field. Valid ABIs: default/armeabi-v7a, default/x86 Project: Jenkins Priority: Minor Reporter: Christopher Orr 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 -- 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-25337) Jenkins fails to start
Bruce Coveny created JENKINS-25337 Jenkins fails to start Issue Type: Bug Assignee: Unassigned Components: core Created: 28/Oct/14 11:21 AM Description: After updating to version 1.586 the Jenkins application fails to load with stack trace of the following: 10/28/14 7:10:57:152 EDT 00a0 SystemErr R Exception in thread "Jenkins initialization thread" java.lang.NoClassDefFoundError: hudson.util.HudsonFailedToLoad 10/28/14 7:10:57:152 EDT 00a0 SystemErr R at hudson.WebAppMain$3.run(WebAppMain.java:234) 10/28/14 7:10:57:152 EDT 00a0 SystemErr R Caused by: java.lang.ClassNotFoundException: hudson.util.HudsonFailedToLoad 10/28/14 7:10:57:152 EDT 00a0 SystemErr R at java.net.URLClassLoader.findClass(URLClassLoader.java:434) 10/28/14 7:10:57:152 EDT 00a0 SystemErr R at com.ibm.ws.bootstrap.ExtClassLoader.findClass(ExtClassLoader.java:204) 10/28/14 7:10:57:152 EDT 00a0 SystemErr R at java.lang.ClassLoader.loadClassHelper(ClassLoader.java:699) 10/28/14 7:10:57:152 EDT 00a0 SystemErr R at java.lang.ClassLoader.loadClass(ClassLoader.java:678) 10/28/14 7:10:57:152 EDT 00a0 SystemErr R at com.ibm.ws.bootstrap.ExtClassLoader.loadClass(ExtClassLoader.java:119) 10/28/14 7:10:57:152 EDT 00a0 SystemErr R at java.lang.ClassLoader.loadClass(ClassLoader.java:661) 10/28/14 7:10:57:152 EDT 00a0 SystemErr R at com.ibm.ws.classloader.ProtectionClassLoader.loadClass(ProtectionClassLoader.java:62) 10/28/14 7:10:57:152 EDT 00a0 SystemErr R at com.ibm.ws.classloader.ProtectionClassLoader.loadClass(ProtectionClassLoader.java:58) 10/28/14 7:10:57:152 EDT 00a0 SystemErr R at com.ibm.ws.classloader.CompoundClassLoader.loadClass(CompoundClassLoader.java:616) 10/28/14 7:10:57:152 EDT 00a0 SystemErr R at java.lang.ClassLoader.loadClass(ClassLoader.java:661) 10/28/14 7:10:57:152 EDT 00a0 SystemErr R ... 1 more 10/28/14 7:10:57:355 EDT 008f SystemErr R com.ibm.ws.exception.RuntimeWarning: com.ibm.ws.webcontainer.exception.WebAppNotLoadedException: Failed to load webapp: Failed to load webapp: SRVE8111E: The application, jenkins_war, is trying to modify a cookie which matches a pattern in the restricted programmatic session cookies list domain=*, name=JSESSIONID, path=/. 10/28/14 7:10:57:355 EDT 008f SystemErr R at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:432) 10/28/14 7:10:57:355 EDT 008f SystemErr R at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:718) 10/28/14 7:10:57:355 EDT 008f SystemErr R at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1175) 10/28/14 7:10:57:355 EDT 008f SystemErr R at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1370) 10/28/14 7:10:57:355 EDT 008f SystemErr R at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:639) 10/28/14 7:10:57:355 EDT 008f SystemErr R at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:968) 10/28/14 7:10:57:355 EDT 008f SystemErr R at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:774) 10/28/14 7:10:57:355 EDT 008f SystemErr R at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplicationDynamically(ApplicationMgrImpl.java:1374) 10/28/14 7:10:57:355 EDT 008f SystemErr R at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:2179) 10/28/14 7:10:57:355 EDT 008f SystemErr R at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:445) 10/28/14 7:10:57:355 EDT 008f SystemErr R at com.ibm.ws.runtime.component.CompositionUnitImpl.start(CompositionUnitImpl.java:123) 10/28/14 7:10:57:355 EDT 008f SystemErr R at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:388) 10/28/14 7:10:57:355 EDT 008f SystemErr R at
[JIRA] [core] (JENKINS-23942) quietDown reports HTTP 405 Method Not Allowed
Bruce Coveny closed JENKINS-23942 as Fixed quietDown reports HTTP 405 Method Not Allowed Tested in 1.585 works now. Change By: Bruce Coveny (28/Oct/14 11:24 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 -- 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-25337) Jenkins fails to start
Bruce Coveny commented on JENKINS-25337 Jenkins fails to start Reverting back to 1.585 Jenkins starts successfully. 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 -- 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-751) hudson.tasks.junit.AbortException thrown on some maven2 projects
Frank Mueller commented on JENKINS-751 hudson.tasks.junit.AbortException thrown on some maven2 projects Aditional Info: If I add the parameter -DskipTests=true Everything works 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 -- 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-751) hudson.tasks.junit.AbortException thrown on some maven2 projects
Frank Mueller edited a comment on JENKINS-751 hudson.tasks.junit.AbortException thrown on some maven2 projects Aditional Info: If I add the parameter -DskipTests=true Everything works fine. But in our Case we would only prevent integration-test from run. Therefore we have something like skipTests=false and maven.test.skip=true. 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 -- 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] (JENKINS-25313) Deleting repository or branch from Git settings also prevents future addition
SCM/JIRA link daemon commented on JENKINS-25313 Deleting repository or branch from Git settings also prevents future addition Code changed in jenkins User: Mark Waite Path: src/main/java/hudson/plugins/git/GitSCM.java http://jenkins-ci.org/commit/git-plugin/e4f8cc5da51bf4d5379d26228da8657dc94bc2e7 Log: Fixed JENKINS-25313 fix null pointer exception when last repo or branch deleted 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 -- 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] (JENKINS-25313) Deleting repository or branch from Git settings also prevents future addition
Mark Waite resolved JENKINS-25313 as Fixed Deleting repository or branch from Git settings also prevents future addition Planned to be included in the git plugin 2.2.8 release Change By: Mark Waite (28/Oct/14 12:49 PM) Status: Open Resolved Resolution: Fixed 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 -- 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] (JENKINS-25313) Deleting repository or branch from Git settings also prevents future addition
SCM/JIRA link daemon commented on JENKINS-25313 Deleting repository or branch from Git settings also prevents future addition Code changed in jenkins User: Mark Waite Path: src/main/java/hudson/plugins/git/GitSCM.java http://jenkins-ci.org/commit/git-plugin/247f03f6a691199e0d7757ec1f17d2dded320989 Log: Fixed JENKINS-25313 fix null pointer exception when last repo or branch deleted 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 -- 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] [cli] (JENKINS-25338) list-jobs cli
Bruce Coveny created JENKINS-25338 list-jobs cli Issue Type: Improvement Assignee: Unassigned Components: cli Created: 28/Oct/14 1:10 PM Description: Currently the list-jobs prints out the "Display Name" in the advanced option configuration of the job. However other commands such as get-job requires the "Project Name". Can the commands be either changed to accept either of these names or have parameters on the list-jobs to select which name to print out. get-job submits an error while using the "Display Name" which states the project name in it. For example if the "Display Name" is "My Build" and project name is "MY_BUILD" if you do get-job "My Build" it gives you the error "No such job 'My Build'; perhaps you meant 'MY_BUILD'? Environment: JENKINS WAR VERSION 1.586 WINDOWS SERVER 2008 R2 ENTERPRISE AMD OPTERON(TM) PROCESSOR 6136 2.4 GHZ (2 PROCESSORS) 4.0 GB RAM 64-BIT OPERATION SYSTEM WEBSPHERE APPLICATION SERVER 8.5.5 Project: Jenkins Priority: Minor Reporter: Bruce Coveny 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 -- 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] [libvirt-slave] (JENKINS-12523) Could not initialize class org.libvirt.Connect
René Korthaus reopened JENKINS-12523 Could not initialize class org.libvirt.Connect I get a similar error after upgrading Jenkins to latest 1.586, I think it is related to https://issues.jenkins-ci.org/browse/JENKINS-24521. Downgrading to 1.585 fixes the issue. Here's the stack: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/lib/jenkins/plugins/libvirt-slave/WEB-INF/lib/libvirt-slave.jar!/hudson/plugins/libvirt/VirtualMachineSlave/configure-entries.jelly:9:124: Could not initialize class org.libvirt.Connect at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.Stapler.service(Stapler.java:237) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) 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 jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) 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 jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:86) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at
[JIRA] [embeddable-build-status] (JENKINS-25339) Icons will not be displayed in IE8 with Version 1.5 in contradiction to 1.4
Karl-Heinz Marbaise created JENKINS-25339 Icons will not be displayed in IE8 with Version 1.5 in contradiction to 1.4 Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: embeddable-build-status Created: 28/Oct/14 1:31 PM Description: Currently i've upgraded to version 1.5 of embeddable-build-status plugin which results in not viewable icons on a IE 8 (Unfortunately i have to stuck with this) ..the previous version 1.4 worked fine. Project: Jenkins Priority: Minor Reporter: Karl-Heinz Marbaise 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 -- 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] [cucumber-testresult-plugin] (JENKINS-25340) lost trend history after skipping build
Kanstantsin Shautsou created JENKINS-25340 lost trend history after skipping build Issue Type: Bug Assignee: teilo Components: cucumber-testresult-plugin Created: 28/Oct/14 1:58 PM Description: I had trend history, then aborted two builds (run job and press abort), after it trend history graph become clear. After 2 builds graph filled back with 2 results (but before abort results still doesn't appeared). Environment: core: 1.565.3 LTS plugin: 0.6.0 Project: Jenkins Priority: Major Reporter: Kanstantsin Shautsou 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 -- 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] [jabber] (JENKINS-25222) Jenkins does not stay in chatrooms after 1.26 upgrade
Nick Jones commented on JENKINS-25222 Jenkins does not stay in chatrooms after 1.26 upgrade I've just put this custom build in place, and will let you know how it goes. 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 -- 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] [perforce-plugin] (JENKINS-25332) Workspace changes does not trigger a full sync
Rob Petti assigned JENKINS-25332 to Unassigned Workspace changes does not trigger a full sync Change By: Rob Petti (28/Oct/14 2:14 PM) Assignee: RobPetti 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 -- 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] (JENKINS-25341) Improve reconcile by using -m option
Morne Joubert created JENKINS-25341 Improve reconcile by using -m option Issue Type: Bug Assignee: Unassigned Components: p4 Created: 28/Oct/14 2:20 PM Description: The reconcile steps is taking very long on our system and is producing load if there is a very big client spec so we can't use this setting. From the perforce documentation is can see there is a reconsile -m option. Could you please implement this by using the modtime sync settings. Project: Jenkins Priority: Major Reporter: Morne Joubert 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 -- 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] (JENKINS-25341) Improve reconcile by using -m option
Morne Joubert updated JENKINS-25341 Improve reconcile by using -m option Change By: Morne Joubert (28/Oct/14 2:21 PM) Issue Type: Bug Improvement 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 -- 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] [clearcase-ucm] (JENKINS-25342) Project templates should be parsed on the executing node
Mads Nielsen created JENKINS-25342 Project templates should be parsed on the executing node Issue Type: Bug Assignee: Praqma Support Components: clearcase-ucm Created: 28/Oct/14 2:25 PM Project: Jenkins Priority: Minor Reporter: Mads Nielsen 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 -- 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-25221) Content of Custom Workspace changes in v1.585
Bernhard Miklautz commented on JENKINS-25221 Content of Custom Workspace changes in v1.585 I've also observed this problem on Debian 7.7 with versions v.1585 and v.1586. No problem with v.1584. For me the problem is easily reproducible: Create a multi-configuration project Set "Use custom workspace" in Advanced Project Options (I've used "xxx" for testing) Save the project If you reopen the project configuration and look at the custom workspace setting it contains '{"directory":["xxx",""]}' 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 -- 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-25241) svn+ssh checkout fails on remote nodes
Brandon Smith commented on JENKINS-25241 svn+ssh checkout fails on remote nodes I am on Jenkins 1.587 (same versions of plugins above also) and have the same issue. 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 -- 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-25343) Dropdown Add parameter not working
Semen Pom created JENKINS-25343 Dropdown Add parameter not working Issue Type: Bug Assignee: Semen Pom Attachments: jenkins.PNG Components: core Created: 28/Oct/14 2:38 PM Description: I have a job with multiple String parameters (i've created it long ago) Today I tried to add new parameter (type of parameter doesn't metter) and after i clicked on Boolean parameter - nothing happened. I opened network profiling in chrome and saw that each time after i clicked parameter (Boolean parameter, String parameter, it does not matter) - network error appeared in profiling. Error is: Request URL: http://our jenkins host/jenkins/$stapler/bound/48920585-3a2e-47b8-9d2d-1037cbfaeb8e/render Request Method:POST Status Code:404 Not Found (more on screenshot i've attached) Environment: Jenins 1.586 deployed as WAR on Tomcat 7 Browser is Chrome 38.0.2125.104 m Project: Jenkins Priority: Major Reporter: Semen 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 -- 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] (JENKINS-24624) Support for shared workspaces
Paul Allen commented on JENKINS-24624 Support for shared workspaces It may be possible to share workspaces using the client -s flag (with -t or -S). The -s flag would switch the view and a sync should only fetch the differences. This would help with the storage requirements for a workspace as there is only one root required per executor. How to implemented under Jenkins is going to need some careful thought. 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 -- 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] [cucumber-testresult-plugin] (JENKINS-25340) lost trend history after skipping build
teilo commented on JENKINS-25340 lost trend history after skipping build hardly suprising... https://github.com/jenkinsci/jenkins/commit/8d8102036f4e52aada39db37c05025b9bb31516d 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 -- 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] [cucumber-testresult-plugin] (JENKINS-25340) lost trend history after skipping build
teilo assigned JENKINS-25340 to Jesse Glick lost trend history after skipping build Change By: teilo (28/Oct/14 2:50 PM) Assignee: teilo 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 -- 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-23945) Test result trend breaks lazy-loading
teilo commented on JENKINS-23945 Test result trend breaks lazy-loading introduced JENKINS-25340 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 -- 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] (JENKINS-25300) Several of my p4 projects do not list *any* changes between builds
Paul Allen commented on JENKINS-25300 Several of my p4 projects do not list *any* changes between builds Sorry if I missed something, but from what I can see in the config files you are using the label/tag feature to create a label called 'basic_check', which gets updated on each build. Then the other build is pinned to this label. I'll see if I can reproduce this. I did notice that the config file references p4@1.0.13? Are you running the latest build, as I have recently changed the way changes are calculated (1.0.16). 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 -- 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] [cucumber-testresult-plugin] (JENKINS-25340) lost trend history after skipping build
teilo updated JENKINS-25340 lost trend history after skipping build Change By: teilo (28/Oct/14 2:56 PM) Component/s: junit-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 -- 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] (JENKINS-25300) Several of my p4 projects do not list *any* changes between builds
Glen Gibb commented on JENKINS-25300 Several of my p4 projects do not list *any* changes between builds Yup, I updated to the 1.0.16 p4 plugin last week before reporting the issue. The config.xml files report the old version as I did not make any config changes after the update. 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 -- 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-25241) svn+ssh checkout fails on remote nodes
Barry Jarman commented on JENKINS-25241 svn+ssh checkout fails on remote nodes I've tried Jenkins 1.586 (same versions of the plugins above except for JRE 1.6.0 IBM J9 2.4 AIX ppc64-64) and also have same issue. Regressed to 1.583, no problems. 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 -- 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] (JENKINS-24624) Support for shared workspaces
Morne Joubert commented on JENKINS-24624 Support for shared workspaces having a workspace per executor is not a problem so far. So if i have a slave with 4 executors and 50 different jobs all using the same stream then i only have 4 jenkins workspaces and 4 P4 client specs. I assume Jenkins keep track of the last synced version outside of Perforce ? I can't see how it would work otherwise 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 -- 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] (JENKINS-25300) Several of my p4 projects do not list *any* changes between builds
Paul Allen commented on JENKINS-25300 Several of my p4 projects do not list *any* changes between builds Could you send me the last build.xml file from the job reporting no changes and the details of the label. e.g. p4 label -o basic_check Label: basic_check ... Revision: @370 I want to see if the buildChange class="int" value is lower than the 'Revision' specified in the label. 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 -- 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] [cucumber-testresult-plugin] (JENKINS-25340) lost trend history after skipping build
Jesse Glick resolved JENKINS-25340 as Wont Fix lost trend history after skipping build Yup. No plans to fix until core provides a safer way of looking for builds by number. Change By: Jesse Glick (28/Oct/14 3:30 PM) Status: Open Resolved Resolution: WontFix 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 -- 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] (JENKINS-25300) Several of my p4 projects do not list *any* changes between builds
Glen Gibb updated JENKINS-25300 Several of my p4 projects do not list *any* changes between builds build.xml file from the 2014-10-27_18-20-10 build Change By: Glen Gibb (28/Oct/14 3:46 PM) Attachment: build.xml 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 -- 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] (JENKINS-25300) Several of my p4 projects do not list *any* changes between builds
Glen Gibb commented on JENKINS-25300 Several of my p4 projects do not list *any* changes between builds build.xml is attached. The basic label revision number is: @3937 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 -- 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] (JENKINS-25300) Several of my p4 projects do not list *any* changes between builds
Paul Allen commented on JENKINS-25300 Several of my p4 projects do not list *any* changes between builds Yes I see the issue... buildChange class="string"basic_check/buildChange I store the label, not the change. When I try to calculate the changes since the last build I access the label, but that has been updated. 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 -- 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-755) Default JDK meaning in project options is confusing.
Dragomir Nedyalkov commented on JENKINS-755 Default JDK meaning in project options is confusing. Not sure, in which direction the issue resolving is going to, but ... Imagine the scenario when you have environment with hundreds of already setup build jobs, running with the one and only (default in this case) JDK available for the CI server . Then comes a day you need to setup 2 new build jobs to run against the latest and greatest Oracle JDK. What practically happens – The latest and greatest JDK installed on the system and configured for the Jenkins, becomes the “Default” one for all available build jobs. And one needs to manually reconfigure hundreds of build jobs, and explicitly to tell them to use the former JDK…. I do not see any workaround to get out of this nasty situation easily. Or am I wrong? 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 -- 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-25026) Console output stops populating after several seconds
Jimmy Gleason commented on JENKINS-25026 Console output stops populating after several seconds I'm having this issue as well. Has anyone made any progress toward finding a fix for this issue? 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 -- 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] [_test] (JENKINS-25344) Multiple Load rules issue
bharath CHALAVADI created JENKINS-25344 Multiple Load rules issue Issue Type: Bug Assignee: Oleg Nenashev Components: _test Created: 28/Oct/14 4:06 PM Description: Hi, I am created job to build my project. But I am stuck with a issue over here. Here is the detailed description. In the configuration of the Job In "Source Code Management" I have selected "Base ClearCase". In this I have loaded multiple load rules. Like /vobs/build_files and /vobs/manage_build_files both are on different "VOBS" Now I want to have different shells to execute for each "Load Rule" Please help me over here Regards Bharath Project: Jenkins Priority: Blocker Reporter: bharath CHALAVADI 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 -- 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] [_test] (JENKINS-25344) Multiple Load rules issue
bharath CHALAVADI commented on JENKINS-25344 Multiple Load rules issue If there are any changes in load rule /vobs/build_files a particular execute shell in "BUILD" needs too be executed. And if are any changes in load rule /vobs/manage_build_files a particular execute shell in "BUILD" needs too be executed 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 -- 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] [clearcase] (JENKINS-25344) Multiple Load rules issue
Oleg Nenashev updated JENKINS-25344 Multiple Load rules issue Please don't forget to set proper components Change By: Oleg Nenashev (28/Oct/14 4:13 PM) Component/s: clearcase Component/s: _test 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 -- 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] [clearcase] (JENKINS-25344) Multiple Load rules issue
bharath CHALAVADI edited a comment on JENKINS-25344 Multiple Load rules issue If there are any changes in load rule /vobs/build_files a particular execute shell in "BUILD" needs too be executed. And if are any changes in load rule /vobs/manage_build_files a particular execute shell in "BUILD" needs too be executed Help me over here. thanks in advance Regards Bharath 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 -- 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] [clearcase] (JENKINS-25344) Multiple Load rules issue
bharath CHALAVADI commented on JENKINS-25344 Multiple Load rules issue Hi Oleg Thanks for your instant reply Could you please be more specific 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 -- 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] [clearcase] (JENKINS-25344) Multiple Load rules issue
bharath CHALAVADI edited a comment on JENKINS-25344 Multiple Load rules issue Hi Oleg Thanks for your instant reply Could you please be more specific If you want me to be more specific..I will 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 -- 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] (JENKINS-25345) Git publisher; Tag message needs double quote to create a tag
adoudev viaccess-orca created JENKINS-25345 Git publisher; Tag message needs double quote to create a tag Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 28/Oct/14 4:34 PM Description: need to add double quote in tag message or create tag failed. tag message = tag message git tag -a -f -m tag message tag # timeout=10 tag message = "tag message" git tag -a -f -m "tag message" tag # timeout=10 Environment: Jenkins ver. 1.565.3 Git plugin 2.2.6 Project: Jenkins Priority: Minor Reporter: adoudev viaccess-orca 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 -- 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-24380) Use build numbers as IDs
Jesse Glick commented on JENKINS-24380 Use build numbers as IDs Daniel Beck (ref: ZD-22496) noted that the current code behaves poorly if build directories are deleted but broken numeric symlinks are left behind. Need to check that behavior in the context of the revised code, where the symlinks would be the timestamps. 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 -- 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-25337) Jenkins fails to start
Daniel Beck commented on JENKINS-25337 Jenkins fails to start Have you investigated the error message? It seems the container prohibits making the cookie e.g. HttpOnly, so looks more like a config issue than anything else. 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 -- 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] [clearcase] (JENKINS-25344) Multiple Load rules issue
bharath CHALAVADI edited a comment on JENKINS-25344 Multiple Load rules issue Hi Oleg Thanks for your instant reply Could you please be more specific Regards Bharath 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 -- 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] [cli] (JENKINS-25338) list-jobs cli
Daniel Beck assigned JENKINS-25338 to Daniel Beck list-jobs cli Change By: Daniel Beck (28/Oct/14 4:42 PM) Assignee: DanielBeck 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 -- 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] [cucumber-testresult-plugin] (JENKINS-25340) lost trend history after skipping build
Kanstantsin Shautsou reopened JENKINS-25340 lost trend history after skipping build This is blocker for me. I'm limiting number of jobs to what i want see in trend - it's near 30, not sure what performance issues it may cause and what you want expect from core. Also we can't use Jenkins test results now. Do you have core issue that maybe linked to this issue? Change By: Kanstantsin Shautsou (28/Oct/14 4:48 PM) Resolution: WontFix Status: Resolved 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 -- 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] [clearcase] (JENKINS-25344) Multiple Load rules issue
bharath CHALAVADI commented on JENKINS-25344 Multiple Load rules issue Hi Oleg Could you please provide me the info regarding the "Proper Components" that you have commented 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 -- 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] [jabber] (JENKINS-25222) Jenkins does not stay in chatrooms after 1.26 upgrade
Nick Jones commented on JENKINS-25222 Jenkins does not stay in chatrooms after 1.26 upgrade @kutzi, the release you prepared for me works great. Is this same keepalive in 1.27 (which looks like it fixed the issue with old messages being processed) or will I need to wait for a subsequent release? 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 -- 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] [cli] (JENKINS-25338) list-jobs cli
Daniel Beck commented on JENKINS-25338 list-jobs cli Ugh. Yeah, we changed that a while back because it was stupid for the reason you mentioned, decided to write a new 'list-items' command, that stalled, and we still have the weird behavior. I'll submit a PR. 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 -- 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] (JENKINS-25341) Improve reconcile by using -m option
Paul Allen commented on JENKINS-25341 Improve reconcile by using -m option Out of interest which P4D version are you using? There were some recent improvements made to reconcile (14.2). The -m flag is a idea as long as the client/files are not using +m or modtime, not 100% sure if p4java supports this, but will look into it? 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 -- 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] [clearcase] (JENKINS-25344) Multiple Load rules issue
Oleg Nenashev commented on JENKINS-25344 Multiple Load rules issue See https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue 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 -- 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] [copy-to-slave] (JENKINS-25346) Copy files back to master node doesn't copy to workspace
Aaron Simmons created JENKINS-25346 Copy files back to master node doesnt copy to workspace Issue Type: Bug Assignee: Vivekanand SV Components: copy-to-slave Created: 28/Oct/14 4:56 PM Description: I've a matrix job that uses the "Copy To Slave" plugin to "Copy files back to master node" as a post-build action. I then use the PostBuildScript plugin to run on the master node to process these files. However, even though Copy-to-Slave succeeds, the files aren't in the master workspace. Look at the build output on the slaves shows: [copy-to-slave] Copying 'build/**/*', excluding nothing, from 'file:/home/foobar/jenkins/workspace/JenkinsSandbox/label/foobar-ci-linux/' on 'hudson.slaves.DumbSlave@564c7adb' to 'file:/Users/foobar/.jenkins/jobs/JenkinsSandbox/configurations/axis-label/foobar-ci-linux/workspace/' on the master. The path /Users/foobar/.jenkins/jobs/JenkinsSandbox/configurations/axis-label/foobar-ci-linux/workspace/ is not the workspace. The workspace is actually here: /Users/foobar/.jenkins/.jenkins/workspace/JenkinsSandbox/ Why does Copy-To-Slave copy the files to this weird path? Project: Jenkins Priority: Critical Reporter: Aaron Simmons 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 -- 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] [clearcase] (JENKINS-25344) Multiple Load rules issue
bharath CHALAVADI commented on JENKINS-25344 Multiple Load rules issue Thanks for the link.please let me know where do we need to raise a JIRA if we need any clarifications regarding the JENKINS configuraions 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 -- 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] [cucumber-testresult-plugin] (JENKINS-25340) lost trend history after skipping build
teilo commented on JENKINS-25340 lost trend history after skipping build the code that is broken in core (in 1.565) no longer lives in core - it now lives in the junit 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 -- 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] [copy-to-slave] (JENKINS-25346) Copy files back to master node doesn't copy to workspace
Aaron Simmons updated JENKINS-25346 Copy files back to master node doesnt copy to workspace Change By: Aaron Simmons (28/Oct/14 4:56 PM) Description: IveamatrixjobthatusestheCopyToSlaveplugintoCopyfilesbacktomasternodeasapost-buildaction.IthenusethePostBuildScriptplugintorunonthemasternode to and processthesefiles.However,eventhoughCopy-to-Slavesucceeds,thefilesarentinthemasterworkspace.Lookatthebuildoutputontheslavesshows:{code}[copy-to-slave]Copyingbuild/**/*,excludingnothing,fromfile:/home/foobar/jenkins/workspace/JenkinsSandbox/label/foobar-ci-linux/onhudson.slaves.DumbSlave@564c7adbtofile:/Users/foobar/.jenkins/jobs/JenkinsSandbox/configurations/axis-label/foobar-ci-linux/workspace/onthemaster.{code}Thepath{code}/Users/foobar/.jenkins/jobs/JenkinsSandbox/configurations/axis-label/foobar-ci-linux/workspace/{code}isnottheworkspace.Theworkspaceisactuallyhere:{code}/Users/foobar/.jenkins/.jenkins/workspace/JenkinsSandbox/{code}WhydoesCopy-To-Slavecopythefilestothisweirdpath? 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 -- 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] [copy-to-slave] (JENKINS-25346) Copy files back to master node doesn't copy to workspace
Aaron Simmons updated JENKINS-25346 Copy files back to master node doesnt copy to workspace Change By: Aaron Simmons (28/Oct/14 4:56 PM) Description: IveamatrixjobthatusestheCopyToSlaveplugintoCopyfilesbacktomasternodeasapost-buildaction.IthenusethePostBuildScriptplugintorunonthemasternodeandprocessthesefiles.However,eventhoughCopy-to-Slavesucceeds,thefilesarentinthemasterworkspace. Look Looking atthebuildoutputontheslavesshows:{code}[copy-to-slave]Copyingbuild/**/*,excludingnothing,fromfile:/home/foobar/jenkins/workspace/JenkinsSandbox/label/foobar-ci-linux/onhudson.slaves.DumbSlave@564c7adbtofile:/Users/foobar/.jenkins/jobs/JenkinsSandbox/configurations/axis-label/foobar-ci-linux/workspace/onthemaster.{code}Thepath{code}/Users/foobar/.jenkins/jobs/JenkinsSandbox/configurations/axis-label/foobar-ci-linux/workspace/{code}isnottheworkspace.Theworkspaceisactuallyhere:{code}/Users/foobar/.jenkins/.jenkins/workspace/JenkinsSandbox/{code}WhydoesCopy-To-Slavecopythefilestothisweirdpath? 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 -- 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] [copy-to-slave] (JENKINS-25346) Copy files back to master node doesn't copy to workspace
Aaron Simmons updated JENKINS-25346 Copy files back to master node doesnt copy to workspace Change By: Aaron Simmons (28/Oct/14 4:57 PM) Description: IveamatrixjobthatusestheCopyToSlaveplugintoCopyfilesbacktomasternodeasapost-buildaction.IthenusethePostBuildScriptplugintorunonthemasternodeandprocessthesefiles.However,eventhoughCopy-to-Slavesucceeds,thefilesarentinthemasterworkspace.Lookingatthebuildoutputontheslavesshows:{code}[copy-to-slave]Copyingbuild/**/*,excludingnothing,fromfile:/home/foobar/jenkins/workspace/ JenkinsSandbox MyJob /label/foobar-ci-linux/onhudson.slaves.DumbSlave@564c7adbtofile:/Users/foobar/.jenkins/jobs/ JenkinsSandbox MyJob /configurations/axis-label/foobar-ci-linux/workspace/onthemaster.{code}Thepath{code}/Users/foobar/.jenkins/jobs/ JenkinsSandbox MyJob /configurations/axis-label/foobar-ci-linux/workspace/{code}isnottheworkspace.Theworkspaceisactuallyhere:{code}/Users/foobar/.jenkins/.jenkins/workspace/ JenkinsSandbox MyJob /{code}WhydoesCopy-To-Slavecopythefilestothisweirdpath? 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 -- 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-25337) Jenkins fails to start
Bruce Coveny commented on JENKINS-25337 Jenkins fails to start Confused by this. So it shouldn't be HttpOnly? Why would this change between Jenkins 1.585 and 1.586. Also according to the property in WebSphere it makes it sound like you want it HttpOnly to prevent cross-site scripting attacks. WebSphere checkbox label: Set session cookies to HTTPOnly to help prevent cross-site scripting attacks 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 -- 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] [jabber] (JENKINS-25222) Jenkins does not stay in chatrooms after 1.26 upgrade
kutzi commented on JENKINS-25222 Jenkins does not stay in chatrooms after 1.26 upgrade No it's not in 1.27. I'll release 1.28 within the next couple of days 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 -- 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] (JENKINS-25300) Several of my p4 projects do not list *any* changes between builds
Glen Gibb commented on JENKINS-25300 Several of my p4 projects do not list *any* changes between builds I'm happy to test any fixes when you've had a chance to make them. 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 -- 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] (JENKINS-25345) Git publisher; Tag message needs quote to create a tag
adoudev viaccess-orca updated JENKINS-25345 Git publisher; Tag message needs quote to create a tag Change By: adoudev viaccess-orca (28/Oct/14 5:06 PM) Summary: Gitpublisher;Tagmessageneeds double quotetocreateatag Description: needtoadd double quoteintagmessageorcreatetagfailed.tagmessage=tagmessagegittag-a-f-mtagmessagetag#timeout=10tagmessage=tagmessagegittag-a-f-mtagmessagetag#timeout=10 Pleasenotethatquotearenecessarytocreatethetagbutalsonotethattheyarepresentinthetag.Sameissuewithsimplequote. 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 -- 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] (JENKINS-25300) Several of my p4 projects do not list *any* changes between builds
SCM/JIRA link daemon commented on JENKINS-25300 Several of my p4 projects do not list *any* changes between builds Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/CheckoutTask.java src/test/java/org/jenkinsci/plugins/p4/client/ConnectionTest.java http://jenkins-ci.org/commit/p4-plugin/be16da4210249bcaff54dc65faf7f5a431b54385 Log: Fix change detection when using a moving label If a build was pinned or built from a label, the label name was recorded buildChange. If the label is updated between builds then comparing against an earlier build will give you the wrong result. This fix stores the automatic label ‘Revision’ field and stores this in buildChange. NOTE: you will need to run a manual build to flush the label, so that the last build has a change number. JENKINS-25300 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 -- 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] (JENKINS-25300) Several of my p4 projects do not list *any* changes between builds
Paul Allen commented on JENKINS-25300 Several of my p4 projects do not list *any* changes between builds I have submitted a fix. As mentioned you will need to flush this through with a manual build, or wait for two polling events. Please let me know if this fixes the issue If all is good I'll try and release it at the end of the week. 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 -- 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] [clearcase] (JENKINS-25344) Multiple Load rules issue
bharath CHALAVADI commented on JENKINS-25344 Multiple Load rules issue SO I think now you can close the JIRA 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 -- 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] (JENKINS-25335) Support for variables when specifying stream
Paul Allen commented on JENKINS-25335 Support for variables when specifying stream Are you looking for an environment variable? What would be your use-case? I only support two environment variables P4_CHANGELIST and P4_CLIENT. I also pass the Review parameters to the environment: p4.status, p4.label, p4.change, p4.review, p4.pass, p4.fail 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 -- 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-25241) svn+ssh checkout fails on remote nodes
Liam Reimers edited a comment on JENKINS-25241 svn+ssh checkout fails on remote nodes Could this be related? https://confluence.atlassian.com/display/FISHKB/java.lang.NoClassDefFoundError+Using+SVNKit+Via+SVN+SSH 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 -- 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-25241) svn+ssh checkout fails on remote nodes
Liam Reimers commented on JENKINS-25241 svn+ssh checkout fails on remote nodes I have the same problem on 1.586. Rolled back to 1.583, no problems. 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 -- 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-25241) svn+ssh checkout fails on remote nodes
Liam Reimers commented on JENKINS-25241 svn+ssh checkout fails on remote nodes Could this 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 -- 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] [claim] (JENKINS-7824) Claim plugin: Allow assigning builds/tests to other users
Breck Yunits commented on JENKINS-7824 Claim plugin: Allow assigning builds/tests to other users Also noticed that 2.4 is not yet available. Would love to use this feature. 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 -- 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-14752) SCM Polling / Max # of concurrent polling = 1 hangs github polling
David Feldsine edited a comment on JENKINS-14752 SCM Polling / Max # of concurrent polling = 1 hangs github polling I am having the same issue. git 1.7.1 Jenkins 1.492 Git Plugin 1.4.0 RedHat 2.6.32-279.5.2.el6.x86_64 I will go for weeks with no issue then I will have a flurry of them. I would say that it fails about .1% to .01% of the time. jenkins 18718 0.0 0.0 10136 1240 ?S16:59 0:00 git fetch -t origin +refs/heads/:refs/remotes/origin/ jenkins 18722 0.0 0.0 60040 3048 ?S16:59 0:00 ssh g...@bitbucket.org git-upload-pack 'company/REPO.git' jenkins 29927 0.0 0.0 37336 3640 ?S16:01 0:00 git fetch -t origin +refs/heads/:refs/remotes/origin/ jenkins 29931 0.0 0.0 60040 3048 ?S16:01 0:00 ssh g...@bitbucket.org git-upload-pack 'company/REPO2.git' {noforat} 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 -- 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-14752) SCM Polling / Max # of concurrent polling = 1 hangs github polling
David Feldsine commented on JENKINS-14752 SCM Polling / Max # of concurrent polling = 1 hangs github polling I am having the same issue. git 1.7.1 Jenkins 1.492 Git Plugin 1.4.0 RedHat 2.6.32-279.5.2.el6.x86_64 I will go for weeks with no issue then I will have a flurry of them. I would say that it fails about .1% to .01% of the time. jenkins 18718 0.0 0.0 10136 1240 ?S16:59 0:00 git fetch -t origin +refs/heads/:refs/remotes/origin/ jenkins 18722 0.0 0.0 60040 3048 ?S16:59 0:00 ssh g...@bitbucket.org git-upload-pack 'company/REPO.git' jenkins 29927 0.0 0.0 37336 3640 ?S16:01 0:00 git fetch -t origin +refs/heads/:refs/remotes/origin/ jenkins 29931 0.0 0.0 60040 3048 ?S16:01 0:00 ssh g...@bitbucket.org git-upload-pack 'company/REPO2.git' {noforat} 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 -- 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] [jabber] (JENKINS-25222) Jenkins does not stay in chatrooms after 1.26 upgrade
Nick Jones commented on JENKINS-25222 Jenkins does not stay in chatrooms after 1.26 upgrade Fantastic, I'll wait on that to upgrade. 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 -- 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.