[JIRA] [cvs] (JENKINS-17533) Jenkins 1.510 deletes all CVS branch checkout files
Michael Clarke commented on JENKINS-17533 Jenkins 1.510 deletes all CVS branch checkout files Can you provide some details about your environment: what version of the CVS Plugin you have, what other build steps are running on the job that's having problems, if you've tried this with any other versions of the CVS plugin, what operating system you're running on, if this is on Jenkins master or a slave, etc. The more detailed and relevant information you provide, the more chance someone has of replicating your setup and reproducing your issue: I certainly haven't come across this issue whilst developing the plugin, or in any of the production environments I've seen it running in. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [scripttrigger] (JENKINS-17566) Severe polling error when using script trigger
Eldad Assis edited a comment on JENKINS-17566 Severe polling error when using script trigger @Arthur - I also have this problem, but I don't have the lines you mentioned in the last build's build.xml. I found that manually triggering the build will release the scripttrigger error until the next time I restart or reload Jenkins. BTW - my environment is Jenkins 1.510 with ScriptTrigger 0.22, running on a windows server 2008 (trigger on a CentOS 6 slave) and another instance running on a windows server 2003 (trigger on master). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [plugin] (JENKINS-17572) plugin fails to create tabs in some cases
Reed Coleman assigned JENKINS-17572 to Reed Coleman plugin fails to create tabs in some cases Change By: Reed Coleman (14/Apr/13 12:14 PM) Assignee: deruyter ReedColeman 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/groups/opt_out.
[JIRA] [core] (JENKINS-16845) NullPointer in getPreviousBuild
Alex Ouzounis commented on JENKINS-16845 NullPointer in getPreviousBuild we are also affected by the broken serial form of FingerprintAction. What happens in our case is that in some cases the dashboard view cannot display the unstable and latest builds. After a couple of refreshes the view gets populated correctly so my assumption is that the lazy loaded "map" of builds loses its integrity and refreshing the dashboard view "forces" it to reload a bit every time until all builds are loaded correctly. We experience this after a jenkins restart or after periods of inactivity. Not sure why it happens in the second case; is the map of builds "cleared" after some time and needs to be re-build ? 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/groups/opt_out.
[JIRA] [scripttrigger] (JENKINS-17566) Severe polling error when using script trigger
Gregory Boissinot commented on JENKINS-17566 Severe polling error when using script trigger @Arthur I think it is not tie directly to the EnvInject plugin. Could you try to reproduce the issue in a simple Jenkins instance? 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/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-17230) Unload component from Config Rotator job does not work (our case 8790)
SCM/JIRA link daemon commented on JENKINS-17230 Unload component from Config Rotator job does not work (our case 8790) Code changed in jenkins User: Christian Wolfgang Path: src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/PrepareWorkspace.java src/test/java/net/praqma/jenkins/configrotator/SystemValidator.java src/test/java/net/praqma/jenkins/configrotator/functional/scm/clearcase/FB8790.java http://jenkins-ci.org/commit/config-rotator-plugin/5ffdb5caf546f8373e27322101be5fe4500dc545 Log: JENKINS-17230 Added path check 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/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-17230) Unload component from Config Rotator job does not work (our case 8790)
SCM/JIRA link daemon commented on JENKINS-17230 Unload component from Config Rotator job does not work (our case 8790) Code changed in jenkins User: Christian Wolfgang Path: src/test/java/net/praqma/jenkins/configrotator/SystemValidator.java src/test/java/net/praqma/jenkins/configrotator/functional/scm/clearcase/FB8790.java http://jenkins-ci.org/commit/config-rotator-plugin/d478bd51e0deb2212e295812235d5e43fef14768 Log: JENKINS-17230 Added view 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/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-17230) Unload component from Config Rotator job does not work (our case 8790)
SCM/JIRA link daemon commented on JENKINS-17230 Unload component from Config Rotator job does not work (our case 8790) Code changed in jenkins User: Christian Wolfgang Path: src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/PrepareWorkspace.java src/test/java/net/praqma/jenkins/configrotator/functional/scm/clearcase/FB8790.java http://jenkins-ci.org/commit/config-rotator-plugin/bb78bdc2d94846386a224e298aa415f24b967140 Log: JENKINS-17230 Updating prepare 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/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-17230) Unload component from Config Rotator job does not work (our case 8790)
SCM/JIRA link daemon commented on JENKINS-17230 Unload component from Config Rotator job does not work (our case 8790) Code changed in jenkins User: Christian Wolfgang Path: src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/PrepareWorkspace.java src/test/java/net/praqma/jenkins/configrotator/functional/scm/clearcase/FB8790.java http://jenkins-ci.org/commit/config-rotator-plugin/e3e8252be69cb4473fbddb304fb821eff39e36f6 Log: JENKINS-17230 Updating FB8790 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/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-17230) Unload component from Config Rotator job does not work (our case 8790)
SCM/JIRA link daemon commented on JENKINS-17230 Unload component from Config Rotator job does not work (our case 8790) Code changed in jenkins User: Christian Wolfgang Path: src/test/java/net/praqma/jenkins/configrotator/functional/scm/clearcase/FB8790.java http://jenkins-ci.org/commit/config-rotator-plugin/325e8361f30f3f3f31deb71bc2d9d66b9a5df624 Log: JENKINS-17230 Added wipe workspace 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/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-17230) Unload component from Config Rotator job does not work (our case 8790)
SCM/JIRA link daemon commented on JENKINS-17230 Unload component from Config Rotator job does not work (our case 8790) Code changed in jenkins User: Christian Wolfgang Path: src/main/java/net/praqma/jenkins/configrotator/ConfigurationRotator.java src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/ClearCaseUCMConfigRotatorChangeLogParser.java http://jenkins-ci.org/commit/config-rotator-plugin/43155ef0a84cc325155ba2da15c2805366d48b1b Log: JENKINS-17230 Added backwards compatibility 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/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-17230) Unload component from Config Rotator job does not work (our case 8790)
SCM/JIRA link daemon commented on JENKINS-17230 Unload component from Config Rotator job does not work (our case 8790) Code changed in jenkins User: Christian Wolfgang Path: src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/PrepareWorkspace.java src/test/java/net/praqma/jenkins/configrotator/SystemValidator.java src/test/java/net/praqma/jenkins/configrotator/functional/scm/clearcase/FB8790.java http://jenkins-ci.org/commit/config-rotator-plugin/bd0fd34c77dba355045001db999e7367659a0c1e Log: JENKINS-17230 Updating prepare 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/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-17604) Fix Git for Config Rotator, case 9045
SCM/JIRA link daemon commented on JENKINS-17604 Fix Git for Config Rotator, case 9045 Code changed in jenkins User: Christian Wolfgang Path: src/main/java/net/praqma/jenkins/configrotator/AbstractConfigurationRotatorSCM.java src/main/java/net/praqma/jenkins/configrotator/scm/git/Checkout.java src/main/java/net/praqma/jenkins/configrotator/scm/git/Git.java src/main/java/net/praqma/jenkins/configrotator/scm/git/GitConfiguration.java src/main/java/net/praqma/jenkins/configrotator/scm/git/GitConfigurationComponent.java src/main/java/net/praqma/jenkins/configrotator/scm/git/ResolveConfigurationComponent.java src/main/java/net/praqma/jenkins/configrotator/scm/git/ResolveNextCommit.java http://jenkins-ci.org/commit/config-rotator-plugin/3612e727609555057a576d5e95a25ee8f35180a2 Log: fixed JENKINS-17604 Added remote checkout class for Git 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/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-17604) Fix Git for Config Rotator, case 9045
SCM/JIRA link daemon resolved JENKINS-17604 as Fixed Fix Git for Config Rotator, case 9045 Change By: SCM/JIRA link daemon (14/Apr/13 12:35 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/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-17604) Fix Git for Config Rotator, case 9045
SCM/JIRA link daemon commented on JENKINS-17604 Fix Git for Config Rotator, case 9045 Code changed in jenkins User: Christian Wolfgang Path: pom.xml src/main/java/net/praqma/jenkins/configrotator/ConfigurationRotator.java src/test/java/net/praqma/jenkins/configrotator/ConfigRotatorProject.java src/test/java/net/praqma/jenkins/configrotator/GitRule.java src/test/java/net/praqma/jenkins/configrotator/SystemValidator.java src/test/java/net/praqma/jenkins/configrotator/functional/scm/git/GitTest.java http://jenkins-ci.org/commit/config-rotator-plugin/7ed417b49ad55bc285fade1feaeaeaa5ea095465 Log: JENKINS-17604 Added test suite for Git 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/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-17604) Fix Git for Config Rotator, case 9045
SCM/JIRA link daemon commented on JENKINS-17604 Fix Git for Config Rotator, case 9045 Code changed in jenkins User: Christian Wolfgang Path: pom.xml http://jenkins-ci.org/commit/config-rotator-plugin/a0d503a78c566c3fa7a1bd7be8b6c83d00bc53e3 Log: JENKINS-17604 Added git tests in 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/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-17604) Fix Git for Config Rotator, case 9045
SCM/JIRA link daemon commented on JENKINS-17604 Fix Git for Config Rotator, case 9045 Code changed in jenkins User: Christian Wolfgang Path: src/main/java/net/praqma/jenkins/configrotator/scm/git/GitConfiguration.java src/main/java/net/praqma/jenkins/configrotator/scm/git/GitConfigurationComponent.java src/main/java/net/praqma/jenkins/configrotator/scm/git/GitTarget.java http://jenkins-ci.org/commit/config-rotator-plugin/c81f647086c3d79a9ca73021d123fe84591a9835 Log: JENKINS-17604 Better equals for Git 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/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-17604) Fix Git for Config Rotator, case 9045
SCM/JIRA link daemon commented on JENKINS-17604 Fix Git for Config Rotator, case 9045 Code changed in jenkins User: Christian Wolfgang Path: pom.xml http://jenkins-ci.org/commit/config-rotator-plugin/c5d51b6acb2eb4e9f5be7f91b7b7561ba59bef9f Log: JENKINS-17604 Updated pom to release versions of cool and pjutils Compare: https://github.com/jenkinsci/config-rotator-plugin/compare/040bb00b2685...c5d51b6acb2e 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/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-14746) Use nothing to build (grey builds) if there is no new baselines, our case 6843
SCM/JIRA link daemon commented on JENKINS-14746 Use nothing to build (grey builds) if there is no new baselines, our case 6843 Code changed in jenkins User: Christian Wolfgang Path: pom.xml http://jenkins-ci.org/commit/config-rotator-plugin/9ea21da847c7a4003ef2adb6c466bd17332b4ca6 Log: JENKINS-14746 Updated dependencies 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/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-14746) Use nothing to build (grey builds) if there is no new baselines, our case 6843
SCM/JIRA link daemon commented on JENKINS-14746 Use nothing to build (grey builds) if there is no new baselines, our case 6843 Code changed in jenkins User: Christian Wolfgang Path: src/main/java/net/praqma/jenkins/configrotator/ConfigurationRotator.java src/main/java/net/praqma/jenkins/configrotator/ConfigurationRotatorPublisher.java src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/ClearCaseUCM.java src/test/resources/setup.xml http://jenkins-ci.org/commit/config-rotator-plugin/15ad9e5889a0f85c6615027268ca169fbde07eca Log: fixed JENKINS-14746 Ensure publisher + 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/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-17229) Config Rotator does not trig on new baseline (our case 8789)
SCM/JIRA link daemon commented on JENKINS-17229 Config Rotator does not trig on new baseline (our case 8789) Code changed in jenkins User: Christian Wolfgang Path: pom.xml src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/ClearCaseUCM.java src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/NextBaseline.java src/test/java/net/praqma/jenkins/configrotator/ClearCaseUCMBuilder.java http://jenkins-ci.org/commit/config-rotator-plugin/8a4a016d14cf70cf241502a2d059b3de304885be Log: fixed JENKINS-17229 Updated to baseline list 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/groups/opt_out.
[JIRA] [svnmerge] (JENKINS-15830) Error: Unable to infer the new branch name from XXX
Alex Ouzounis commented on JENKINS-15830 Error: Unable to infer the new branch name from XXX any help would be greatly appreciated 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/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-17230) Unload component from Config Rotator job does not work (our case 8790)
Christian Wolfgang resolved JENKINS-17230 as Fixed Unload component from Config Rotator job does not work (our case 8790) Change By: Christian Wolfgang (14/Apr/13 12:48 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/groups/opt_out.
[JIRA] [logging] (JENKINS-17594) incessant jenkins.model.PeepholePermalink updateCache WARNINGS
Christian Wolfgang commented on JENKINS-17594 incessant jenkins.model.PeepholePermalink updateCache WARNINGS Hi, could you please tell me what your setup is? That is for the job and the logging 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/groups/opt_out.
[JIRA] [audit-trail] (JENKINS-16938) Information lost when build is stopped by user (our case 8705)
Christian Wolfgang commented on JENKINS-16938 Information lost when build is stopped by user (our case 8705) Hi, could you please tell me your setup regarding the logging plugin? This plugin does not log anything to the console output! 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/groups/opt_out.
[JIRA] [logging] (JENKINS-17594) incessant jenkins.model.PeepholePermalink updateCache WARNINGS, case 9042
Christian Wolfgang updated JENKINS-17594 incessant jenkins.model.PeepholePermalink updateCache WARNINGS, case 9042 Change By: Christian Wolfgang (14/Apr/13 12:57 PM) Summary: incessantjenkins.model.PeepholePermalinkupdateCacheWARNINGS ,case9042 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/groups/opt_out.
[JIRA] [publish-over-ssh] (JENKINS-17058) Publish over SSH plugin XML configuration cannot be read on jenkins start up.
Alexander Fischer commented on JENKINS-17058 Publish over SSH plugin XML configuration cannot be read on jenkins start up. I have patched and tested only the publish-over-ftp. But I also modified the pom-files for building against the Jenkins API (not anymore the Hudson-API). I can attach the modified pom for the Maven-build. Can I create my own GitHub-repository and publish the patched plugin (sources, pom, ...) until bap has checked and merged my modifications? I will also patch publish-over-ssh and check again. 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/groups/opt_out.
[JIRA] [logging] (JENKINS-17594) incessant jenkins.model.PeepholePermalink updateCache WARNINGS, case 9042
Dan Lewis commented on JENKINS-17594 incessant jenkins.model.PeepholePermalink updateCache WARNINGS, case 9042 setup? dedicated master with 9 slaves, all windows 7 building Java programs using freestyle ant using svn i get these warnings for all of my jobs, starting with build 1.510 (we skipped from 1.506 to 1.510). i have even resaved all of my jobs using 1.510 to no avail. i changed my logging to exclude everything from jenkins.model.PeepholePermalink below severe 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/groups/opt_out.
[JIRA] [m2release] (JENKINS-17264) m2release build fails with java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject
puce commented on JENKINS-17264 m2release build fails with java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject I still encountered this error on 1.510. Is there a work-around? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [m2release] (JENKINS-17264) m2release build fails with java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject
puce commented on JENKINS-17264 m2release build fails with java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject OK, specifying an arbitrary paramter like boolean: workaround=true did the trick. (work-around) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-15355) AdjunctManager: exception upon startup
Maciej Ligenza commented on JENKINS-15355 AdjunctManager: exception upon startup Same here on v1.510: Apr 14, 2013 8:45:25 PM org.kohsuke.stapler.jelly.AdjunctTag doTag WARNING: AdjunctManager is not installed for this application. Skipping adjunct tags java.lang.Exception at org.kohsuke.stapler.jelly.AdjunctTag.doTag(AdjunctTag.java:74) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyRequestDispatcher.forward(JellyRequestDispatcher.java:55) at hudson.util.HudsonIsLoading.doDynamic(HudsonIsLoading.java:45) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:363) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:162) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)
[JIRA] [m2release] (JENKINS-17264) m2release build fails with java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject
Richard Mortimer commented on JENKINS-17264 m2release build fails with java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject The revised m2release-plugin has not been released yet. You can download a pre-release build of it from the link in the plugin page down at the release notes section https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin Specifically you need the .hpi file from https://jenkins.ci.cloudbees.com/job/plugins/job/m2release-plugin/lastStableBuild/org.jvnet.hudson.plugins.m2release$m2release/ Upload that .hpi from your jenkins plugin management centre and restart jenkins. 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/groups/opt_out.
[JIRA] [core] (JENKINS-17526) Broken CSS when reloading Jenkins after a time of inactivity
Dan Newmarch commented on JENKINS-17526 Broken CSS when reloading Jenkins after a time of inactivity I also have this issue with 1.480.3 LTS. With Jenkins running on Windows XP as service. If it makes any difference, I've found that some elements seem to lose their styling before others. In particular the breadcrumb navigation buttons at the top left of the screen seem to lose their styling first. This is quite annoying as the unstyled list of navigation items spans the width of the screen and overlays clickable elements on some screens preventing them from being clicked. I have also observed the entire page being unstyled as with above screenshot. 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/groups/opt_out.
[JIRA] [sloccount] (JENKINS-17427) sloccount NPE
sogabe commented on JENKINS-17427 sloccount NPE Is this reporoduced with the last 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/groups/opt_out.
[JIRA] [build-publisher] (JENKINS-17607) java.lang.StackOverflowError ...at jenkins.model.lazy.AbstractLazyLoadRunMap$Index.ceilingEntry(AbstractLazyLoadRunMap.java:153)
ymajoros created JENKINS-17607 java.lang.StackOverflowError ...at jenkins.model.lazy.AbstractLazyLoadRunMap$Index.ceilingEntry(AbstractLazyLoadRunMap.java:153) Issue Type: Bug Assignee: vjuranek Components: build-publisher Created: 15/Apr/13 5:44 AM Description: I just upgraded from 1.450 (+-) to 1.510. Got this error on an otherwhise working build. It works ok if I uncheck git tagging at the end of the build. INFO INFO BUILD SUCCESS INFO INFO Total time: 12.979s INFO Finished at: Mon Apr 15 07:27:22 CEST 2013 INFO Final Memory: 122M/712M INFO Archiving artifacts Recording test results Pushing tag DEV-80 to repo origin FATAL: null java.lang.StackOverflowError at java.util.TreeMap$AscendingSubMap.init(TreeMap.java:1699) at java.util.TreeMap.tailMap(TreeMap.java:905) at java.util.TreeMap.tailMap(TreeMap.java:940) at jenkins.model.lazy.AbstractLazyLoadRunMap$Index.ceilingEntry(AbstractLazyLoadRunMap.java:153) at jenkins.model.lazy.AbstractLazyLoadRunMap$Index.access$400(AbstractLazyLoadRunMap.java:121) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:356) at jenkins.model.lazy.AbstractLazyLoadRunMap.newestBuild(AbstractLazyLoadRunMap.java:321) at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:1054) at hudson.model.AbstractProject.hasParticipant(AbstractProject.java:1575) at hudson.model.User.getProjects(User.java:448) at hudson.scm.MailAddressResolverImpl.findMailAddressFor(MailAddressResolverImpl.java:21) at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:101) at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:532) at hudson.plugins.git.GitChangeSet.isMailerPropertySet(GitChangeSet.java:290) at hudson.plugins.git.GitChangeSet.findOrCreateUser(GitChangeSet.java:276) at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:324) at hudson.model.AbstractBuild.hasParticipant(AbstractBuild.java:457) at hudson.model.AbstractProject.hasParticipant(AbstractProject.java:1576) at hudson.model.User.getProjects(User.java:448) at hudson.scm.MailAddressResolverImpl.findMailAddressFor(MailAddressResolverImpl.java:21) at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:101) at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:532) at hudson.plugins.git.GitChangeSet.isMailerPropertySet(GitChangeSet.java:290) at hudson.plugins.git.GitChangeSet.findOrCreateUser(GitChangeSet.java:276) at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:324) at hudson.model.AbstractBuild.hasParticipant(AbstractBuild.java:457) at hudson.model.AbstractProject.hasParticipant(AbstractProject.java:1576) at hudson.model.User.getProjects(User.java:448) at hudson.scm.MailAddressResolverImpl.findMailAddressFor(MailAddressResolverImpl.java:21) at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:101) at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:532) at hudson.plugins.git.GitChangeSet.isMailerPropertySet(GitChangeSet.java:290) at hudson.plugins.git.GitChangeSet.findOrCreateUser(GitChangeSet.java:276) at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:324) at hudson.model.AbstractBuild.hasParticipant(AbstractBuild.java:457) at hudson.model.AbstractProject.hasParticipant(AbstractProject.java:1576) at hudson.model.User.getProjects(User.java:448) Project: Jenkins Priority: Major Reporter: ymajoros
