[JIRA] [jira] (JENKINS-16683) the Build Blocker Plugin is missing from Jira
Larry Shatzer, Jr. commented on JENKINS-16683 the Build Blocker Plugin is missing from Jira https://issues.jenkins-ci.org/browse/JENKINS/component/17470, it's just build-blocker. 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] (JENKINS-16436) Build - Prerequisites Check
Larry Shatzer, Jr. assigned JENKINS-16436 to Unassigned Build - Prerequisites Check Change By: Larry Shatzer, Jr. (22/Jan/13 3:35 PM) Assignee: LarryShatzer,Jr. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16083) HTML Publisher v1.1 regression
Larry Shatzer, Jr. commented on JENKINS-16083 HTML Publisher v1.1 regression 1.2 fixes my issue too. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16083) HTML Publisher v1.1 regression
Larry Shatzer, Jr. commented on JENKINS-16083 HTML Publisher v1.1 regression My regression is slightly different. Here is the output in my build: [htmlpublisher] Archiving HTML reports... ERROR: more than one path matched the pattern: ERROR: - /home/jenkins/workspace/projectName/target/dependency-report/index.html ERROR: - /home/jenkins/workspace/projectName/target/dependency-report/ivy-report.css ERROR: - /home/jenkins/workspace/projectName/target/dependency-report/org.grails.internal-AppName-build.graphml ERROR: - /home/jenkins/workspace/projectName/target/dependency-report/org.grails.internal-AppName-build.html ERROR: - /home/jenkins/workspace/projectName/target/dependency-report/org.grails.internal-AppName-compile.graphml ERROR: - /home/jenkins/workspace/projectName/target/dependency-report/org.grails.internal-AppName-compile.html ERROR: - /home/jenkins/workspace/projectName/target/dependency-report/org.grails.internal-AppName-provided.graphml ERROR: - /home/jenkins/workspace/projectName/target/dependency-report/org.grails.internal-AppName-provided.html ERROR: - /home/jenkins/workspace/projectName/target/dependency-report/org.grails.internal-AppName-runtime.graphml ERROR: - /home/jenkins/workspace/projectName/target/dependency-report/org.grails.internal-AppName-runtime.html ERROR: - /home/jenkins/workspace/projectName/target/dependency-report/org.grails.internal-AppName-test.graphml ERROR: - /home/jenkins/workspace/projectName/target/dependency-report/org.grails.internal-AppName-test.html Build step 'Publish HTML reports' changed build result to FAILURE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15926) Build Failure Analyzer with Timestamper output ugly.
Larry Shatzer, Jr. updated JENKINS-15926 Build Failure Analyzer with Timestamper output ugly. Change By: Larry Shatzer, Jr. (26/Nov/12 7:19 PM) Component/s: timestamper This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15926) Build Failure Analyzer with Timestamper output ugly.
Larry Shatzer, Jr. created JENKINS-15926 Build Failure Analyzer with Timestamper output ugly. Issue Type: Bug Assignee: Tomas Westling Components: build-failure-analyzer Created: 26/Nov/12 7:18 PM Description: When looking at a log that has the timestamper plugin enabled, I see something like this when I click on the line that trigger the build failure analyzer. [8mha:dB+LCABb85aBtbiIQSOjNKU4P0+vIKc0PTOvWK8kMze1uCQxtyC1SC8ExvbLL0llgABGJgZGLwaB3MycnMzi4My85FTXgvzkjIoiBimoScn5ecX5Oal6zhAaVS9DRQGQtrZTnRAIAA6DkZ+B[0mmessage : Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project project-name: Compilation failure Project: Jenkins Priority: Major Reporter: Larry Shatzer, Jr. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15367) Jenkins kicks off the wrong downstream builds for Maven
Larry Shatzer, Jr. commented on JENKINS-15367 Jenkins kicks off the wrong downstream builds for Maven This was committed after the 1.491 RC branch was created, and was not backported into the RC branch unfortunately. It will be in 1.492. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15728) Remote slave with Maven Repo Cleaner enabled as post build task fails.
Larry Shatzer, Jr. created JENKINS-15728 Remote slave with Maven Repo Cleaner enabled as post build task fails. Issue Type: Bug Assignee: Unassigned Components: maven-repo-cleaner Created: 05/Nov/12 9:57 PM Description: The slave is a remote linux server (host is linux too, although differing distros). It is connected to via SSH. I got this stacktrace in my build output: 14:50:30 Deleting old workspace snapshot from #440. 14:50:30 ERROR: Publisher org.jenkinsci.plugins.mavenrepocleaner.MavenRepoCleanerPostBuildTask aborted due to exception 14:50:30 hudson.util.IOException2: remote file operation failed: /home/jenkins/workspace/jobname/.repository at hudson.remoting.Channel@2a1f0c81:slavename 14:50:30 at hudson.FilePath.act(FilePath.java:847) 14:50:30 at hudson.FilePath.act(FilePath.java:824) 14:50:30 at org.jenkinsci.plugins.mavenrepocleaner.MavenRepoCleanerPostBuildTask.perform(MavenRepoCleanerPostBuildTask.java:44) 14:50:30 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) 14:50:30 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) 14:50:30 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:779) 14:50:30 at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:994) 14:50:30 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726) 14:50:30 at hudson.model.Run.execute(Run.java:1541) 14:50:30 at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) 14:50:30 at hudson.model.ResourceController.execute(ResourceController.java:88) 14:50:30 at hudson.model.Executor.run(Executor.java:236) 14:50:30 Caused by: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@4d0b24be 14:50:30 at hudson.remoting.UserRequest.serialize(UserRequest.java:166) 14:50:30 at hudson.remoting.UserRequest.init(UserRequest.java:62) 14:50:30 at hudson.remoting.Channel.call(Channel.java:663) 14:50:30 at hudson.FilePath.act(FilePath.java:840) 14:50:30 ... 11 more 14:50:30 Caused by: java.io.NotSerializableException: org.jenkinsci.plugins.mavenrepocleaner.MavenRepoCleanerPostBuildTask 14:50:30 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1156) 14:50:30 at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) 14:50:30 at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) 14:50:30 at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) 14:50:30 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) 14:50:30 at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) 14:50:30 at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) 14:50:30 at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) 14:50:30 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) 14:50:30 at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326) 14:50:30 at hudson.remoting.UserRequest._serialize(UserRequest.java:155) 14:50:30 at hudson.remoting.UserRequest.serialize(UserRequest.java:164) 14:50:30 ... 14 more Project: Jenkins Priority: Major Reporter: Larry Shatzer, Jr. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15687) Config File Provider and SCM Sync causes lots of changes to config files
Larry Shatzer, Jr. created JENKINS-15687 Config File Provider and SCM Sync causes lots of changes to config files Issue Type: Bug Assignee: domi Components: config-file-provider, scm-sync-configuration Created: 31/Oct/12 7:15 PM Description: I have Config File Provider configured to have a global and local settings configurations set for various maven projects. When the job builds it causes a commit to the config file where it adds alternateSettings config setting, and then another to remove that line after the build is done. it is causing lots of noise. Project: Jenkins Priority: Major Reporter: Larry Shatzer, Jr. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15367) Jenkins kicks off the wrong downstream builds for Maven
Larry Shatzer, Jr. commented on JENKINS-15367 Jenkins kicks off the wrong downstream builds for Maven See this thread https://groups.google.com/forum/?fromgroups=#!topic/jenkinsci-dev/sPD02rg0ZCQ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15035) cobertura plugin don't validate report files and later fail to parse them
Larry Shatzer, Jr. commented on JENKINS-15035 cobertura plugin dont validate report files and later fail to parse them I now get a stacktrace on remote slave running a grails build that produces a coverage.xml file. It worked till I upgraded, then when I rolled back, it works again. Here is the stacktrace: Cobertura: Loaded information on 170 classes. 08:10:16 Cobertura: Saved information on 170 classes. 08:10:16 Publishing Cobertura coverage report... 08:10:16 FATAL: Unable to find coverage results 08:10:16 hudson.util.IOException2: remote file operation failed: /home/jenkins/workspace/grailsApplication at hudson.remoting.Channel@2fcf1d75:remoteslave 08:10:16 at hudson.FilePath.act(FilePath.java:847) 08:10:16 at hudson.FilePath.act(FilePath.java:824) 08:10:16 at hudson.plugins.cobertura.CoberturaPublisher.perform(CoberturaPublisher.java:335) 08:10:16 at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) 08:10:16 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:807) 08:10:16 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:782) 08:10:16 at hudson.model.Build$BuildExecution.post2(Build.java:183) 08:10:16 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:729) 08:10:16 at hudson.model.Run.execute(Run.java:1541) 08:10:16 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 08:10:16 at hudson.model.ResourceController.execute(ResourceController.java:88) 08:10:16 at hudson.model.Executor.run(Executor.java:236) 08:10:16 Caused by: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@64916e12 08:10:16 at hudson.remoting.UserRequest.serialize(UserRequest.java:166) 08:10:16 at hudson.remoting.UserRequest.init(UserRequest.java:62) 08:10:16 at hudson.remoting.Channel.call(Channel.java:663) 08:10:16 at hudson.FilePath.act(FilePath.java:840) 08:10:16 ... 11 more 08:10:16 Caused by: java.io.NotSerializableException: hudson.plugins.cobertura.CoberturaPublisher 08:10:16 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1156) 08:10:16 at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) 08:10:16 at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) 08:10:16 at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) 08:10:16 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) 08:10:16 at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) 08:10:16 at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) 08:10:16 at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) 08:10:16 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) 08:10:16 at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326) 08:10:16 at hudson.remoting.UserRequest._serialize(UserRequest.java:155) 08:10:16 at hudson.remoting.UserRequest.serialize(UserRequest.java:164) 08:10:16 ... 14 more 08:10:16 No coverage results were found using the pattern 'target/test-reports/cobertura/coverage.xml' relative to '/home/jenkins/workspace/grailsApplication'. Did you enter a pattern relative to the correct directory? Did you generate the XML report(s) for Cobertura? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15508) issues.jenkins-ci.org does not have a component for embeddable-build-status
Larry Shatzer, Jr. resolved JENKINS-15508 as Fixed issues.jenkins-ci.org does not have a component for embeddable-build-status Component created. Change By: Larry Shatzer, Jr. (12/Oct/12 2:29 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
[JIRA] (JENKINS-15454) Use Tools Installer
Larry Shatzer, Jr. created JENKINS-15454 Use Tools Installer Issue Type: New Feature Assignee: Vaclav Tunka Components: tattletale Created: 10/Oct/12 12:51 AM Description: Using https://wiki.jenkins-ci.org/display/JENKINS/Adding+tool+auto-installer as a template, I can see a backend crawler (https://github.com/jenkinsci/backend-crawler) that gets versions of tattletale jars from https://repository.jboss.org/nexus/content/groups/public/org/jboss/tattletale/tattletale/maven-metadata.xml file Then it can download the jar, and even inspect the pom and get the version of aspectj it needs too. (Possibly making that configurable, defaulting to auto). Then implementing the classes needed for this plugin to use the backend crawler json file to allow automatic install and configuration of this plugin. I'll be working on this a little bit here and there, but wanted to get the feature into JIRA. Project: Jenkins Priority: Major Reporter: Larry Shatzer, Jr. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15435) 1.485 Jenkins Debian packages not found
Larry Shatzer, Jr. resolved JENKINS-15435 as Fixed 1.485 Jenkins Debian packages not found Change By: Larry Shatzer, Jr. (08/Oct/12 6:04 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
[JIRA] (JENKINS-14643) Version 1.476 does not exist
Larry Shatzer, Jr. resolved JENKINS-14643 as Fixed Version 1.476 does not exist Change By: Larry Shatzer, Jr. (08/Oct/12 6:07 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
[JIRA] (JENKINS-2074) Redmine External site integrations
Larry Shatzer, Jr. resolved JENKINS-2074 as Fixed Redmine External site integrations https://wiki.jenkins-ci.org/display/JENKINS/Redmine+Plugin Change By: Larry Shatzer, Jr. (08/Oct/12 6:51 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
[JIRA] (JENKINS-2920) Allow groovy scripts to be saved
Larry Shatzer, Jr. commented on JENKINS-2920 Allow groovy scripts to be saved Scriptler plugin solves this: https://wiki.jenkins-ci.org/display/JENKINS/Scriptler+Plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14978) Maven Deployment Linker does not support 'dynamic' Project name (upstream uploader)
Larry Shatzer, Jr. assigned JENKINS-14978 to Dominik Bartholdi Maven Deployment Linker does not support dynamic Project name (upstream uploader) Change By: Larry Shatzer, Jr. (18/Sep/12 6:59 PM) Assignee: LarryShatzer,Jr. DominikBartholdi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14956) 404 error when trying to mark a job as favorite
Larry Shatzer, Jr. commented on JENKINS-14956 404 error when trying to mark a job as favorite Give http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jvnet/hudson/plugins/favorite/1.13/favorite-1.13.hpi a go... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14956) 404 error when trying to mark a job as favorite
Larry Shatzer, Jr. commented on JENKINS-14956 404 error when trying to mark a job as favorite Thanks for making the plugin better. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14956) 404 error when trying to mark a job as favorite
Larry Shatzer, Jr. closed JENKINS-14956 as Fixed 404 error when trying to mark a job as favorite Change By: Larry Shatzer, Jr. (11/Sep/12 3:53 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14956) 404 error when trying to mark a job as favorite
Larry Shatzer, Jr. commented on JENKINS-14956 404 error when trying to mark a job as favorite The reason for the redirect is due to that is how "Project Actions" work, it needs a URL to send you to. I don't have control over the html of the link in the project page like I do in the columns. I have the fix committed to github, but will wait to release after the github problems are 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
[JIRA] (JENKINS-14956) 404 error when trying to mark a job as favorite
Larry Shatzer, Jr. commented on JENKINS-14956 404 error when trying to mark a job as favorite Released... you can grab the HPI file from http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jvnet/hudson/plugins/favorite/1.11/favorite-1.11.hpi if you didn't want to wait for the mirrors to get it. Let me know if this fixes it for you (btw, it was your using a different context than just / for jenkins and having it /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
[JIRA] (JENKINS-14956) 404 error when trying to mark a job as favorite
Larry Shatzer, Jr. commented on JENKINS-14956 404 error when trying to mark a job as favorite Actually use: http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jvnet/hudson/plugins/favorite/1.12/favorite-1.12.hpi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14637) Maven Deployment Linker does not support all permalinks types
Larry Shatzer, Jr. commented on JENKINS-14637 Maven Deployment Linker does not support all permalinks types The name "linker" in the plugin name does not mean permlinks, but hyperlinks that it puts in the job page. The m2 release plugin already puts a link to the build that caused the release. It seems like a bug for the m2 release plugin, since this plugin is only to put hyperlinks on the build/job pages. It does this by scanning the log of the build for all artifacts uploaded to a maven repository by means of a regex. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14637) Maven Deployment Linker does not support all permalinks types
Larry Shatzer, Jr. edited a comment on JENKINS-14637 Maven Deployment Linker does not support all permalinks types The name "linker" in the plugin name does not mean permlinks, but hyperlinks that it puts in the job page. The m2 release plugin already puts a link to the build that caused the release. It seems like a bug for the m2 release plugin, since this plugin is only to put hyperlinks on the build/job pages. It does this by scanning the log of the build for all artifacts uploaded to a maven repository by means of a regex. Also some maven jobs (usually multi-module ones) produce multiple artifacts, so how would it know which one(s) to put in the permalink, if there was one? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14637) Maven Deployment Linker does not support all permalinks types
Larry Shatzer, Jr. assigned JENKINS-14637 to Dominik Bartholdi Maven Deployment Linker does not support all permalinks types Ahhh, that functionality was not added by me, but Dominik Bartholdi (imod). I'll assign it to him to look at. Change By: Larry Shatzer, Jr. (03/Aug/12 2:08 PM) Assignee: LarryShatzer,Jr. DominikBartholdi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14522) NullPointer on TestTrend portlet
Larry Shatzer, Jr. created JENKINS-14522 NullPointer on TestTrend portlet Issue Type: Bug Assignee: Peter Hayes Components: dashboard-view Created: 20/Jul/12 3:38 PM Description: I get the following stack trace with the recent version of the plugin. Status Code: 500 Exception: java.lang.NullPointerException Stacktrace: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:616) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:203) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:625) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:202) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:175) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at
[JIRA] (JENKINS-14522) NullPointer on TestTrend portlet
Larry Shatzer, Jr. commented on JENKINS-14522 NullPointer on TestTrend portlet If I resave the view, it works fine. Looks like some option is not being defaulted in correctly when upgrading. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14522) NullPointer on TestTrend portlet
Larry Shatzer, Jr. updated JENKINS-14522 NullPointer on TestTrend portlet With this workaround, lowering the Priority to the default instead of Critical. Change By: Larry Shatzer, Jr. (20/Jul/12 3:48 PM) 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
[JIRA] (JENKINS-14522) NullPointer on TestTrend portlet
Larry Shatzer, Jr. commented on JENKINS-14522 NullPointer on TestTrend portlet The plugin should detect nulls on new parameters and default them then. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14031) Anonymouse triggers 500 error
Larry Shatzer, Jr. resolved JENKINS-14031 as Fixed Anonymouse triggers 500 error Change By: Larry Shatzer, Jr. (10/Jul/12 2:07 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
[JIRA] (JENKINS-14031) Anonymouse triggers 500 error
Larry Shatzer, Jr. commented on JENKINS-14031 Anonymouse triggers 500 error I got 1.9 released, please give that a try, once it shows up in your update center. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14031) Anonymouse triggers 500 error
Larry Shatzer, Jr. commented on JENKINS-14031 Anonymouse triggers 500 error Try upgrading to 1.8, and I have 1.9 releasing right now (so you can try to build it from source or wait). There were some null checks I added for another issue, and a few other logic changes in both versions. If there is still an issue, see if the stacktrace differs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14031) Anonymouse triggers 500 error
Larry Shatzer, Jr. commented on JENKINS-14031 Anonymouse triggers 500 error Can you post screenshots of your role strategy configuration and list of all your plugins? The more I have and can try to replicate it, the better. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14031) Anonymouse triggers 500 error
[ https://issues.jenkins-ci.org/browse/JENKINS-14031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163596#comment-163596 ] Larry Shatzer, Jr. commented on JENKINS-14031: -- In the stacktrace I see hudson.plugins.greenballs.GreenBallFilter.doFilter Try removing the Green Balls plugin, and see if that fixes the problem. If so, then probably best to move this ticket to that plugin. Anonymouse triggers 500 error - Key: JENKINS-14031 URL: https://issues.jenkins-ci.org/browse/JENKINS-14031 Project: Jenkins Issue Type: Bug Components: favorite Reporter: Christian Höltje Assignee: Larry Shatzer, Jr. I have the Role Strategy Plugin and Anonymous is configured with view permissions. But it causes a 500 error when visiting the default page for Jenkins (which I've configured to be Favorites)... Status Code: 500 Exception: org.apache.commons.jelly.JellyTagException: jar:file:/opt/local/stow/apache-tomcat-7.0.6/share/apache-tomcat-7.0.6/webapps/automan/WEB-INF/lib/jenkins-core-1.467.jar!/hudson/model/View/index.jelly:44:43: st:include Cannot invoke method isEmpty() on null object Stacktrace: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/opt/local/stow/apache-tomcat-7.0.6/share/apache-tomcat-7.0.6/webapps/automan/WEB-INF/lib/jenkins-core-1.467.jar!/hudson/model/View/index.jelly:44:43: st:include Cannot invoke method isEmpty() on null object at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] (JENKINS-9829) The maven-deployment-linker plugin doesn't support the deployment from the post build task
[ https://issues.jenkins-ci.org/browse/JENKINS-9829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163565#comment-163565 ] Larry Shatzer, Jr. commented on JENKINS-9829: - Is this still an issue? The maven-deployment-linker plugin doesn't support the deployment from the post build task -- Key: JENKINS-9829 URL: https://issues.jenkins-ci.org/browse/JENKINS-9829 Project: Jenkins Issue Type: Bug Components: maven-deployment-linker Reporter: Arnaud Héritier Assignee: Larry Shatzer, Jr. If artifacts are not deployed within the build but after using the post build task the maven-deployment-linker doesn't work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14031) Anonymouse triggers 500 error
[ https://issues.jenkins-ci.org/browse/JENKINS-14031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163571#comment-163571 ] Larry Shatzer, Jr. commented on JENKINS-14031: -- Hmmm... I can't see my code anywhere in the stacktrace, so I'm not sure were to look in my code. I'm also running role strategy plugin, and 1.467, and not having problems. Anonymouse triggers 500 error - Key: JENKINS-14031 URL: https://issues.jenkins-ci.org/browse/JENKINS-14031 Project: Jenkins Issue Type: Bug Components: favorite Reporter: Christian Höltje Assignee: Larry Shatzer, Jr. I have the Role Strategy Plugin and Anonymous is configured with view permissions. But it causes a 500 error when visiting the default page for Jenkins (which I've configured to be Favorites)... Status Code: 500 Exception: org.apache.commons.jelly.JellyTagException: jar:file:/opt/local/stow/apache-tomcat-7.0.6/share/apache-tomcat-7.0.6/webapps/automan/WEB-INF/lib/jenkins-core-1.467.jar!/hudson/model/View/index.jelly:44:43: st:include Cannot invoke method isEmpty() on null object Stacktrace: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/opt/local/stow/apache-tomcat-7.0.6/share/apache-tomcat-7.0.6/webapps/automan/WEB-INF/lib/jenkins-core-1.467.jar!/hudson/model/View/index.jelly:44:43: st:include Cannot invoke method isEmpty() on null object at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] (JENKINS-13813) NullPointer after upgrading to 1.6
lshatzer created JENKINS-13813:
--
Summary: NullPointer after upgrading to 1.6
Key: JENKINS-13813
URL: https://issues.jenkins-ci.org/browse/JENKINS-13813
Project: Jenkins
Issue Type: Bug
Components: grails
Reporter: lshatzer
Assignee: jeffg2one
Priority: Critical
After upgrading to 1.6, when my Grails jobs run, I get a NPE:
{code}
java.lang.NullPointerException
at com.g2one.hudson.grails.GrailsBuilder.perform(GrailsBuilder.java:155)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
at
hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:710)
at hudson.model.Build$RunnerImpl.build(Build.java:178)
at hudson.model.Build$RunnerImpl.doRun(Build.java:139)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:480)
at hudson.model.Run.run(Run.java:1434)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:239)
{code}
I save my job after opening it up and saving it without changing, it now works.
The config file now has an empty: useWrapper element. Your plugin should
probably handle it missing without having to resave all grails jobs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12787) LOADING overlay does not go away on the Configure System page
[
https://issues.jenkins-ci.org/browse/JENKINS-12787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162733#comment-162733
]
lshatzer commented on JENKINS-12787:
I recently went through and removed (from the file system) all disabled
plugins, and this problem went away after I did that, and restarted. I'm not
sure which plugin caused that.
LOADING overlay does not go away on the Configure System page
-
Key: JENKINS-12787
URL: https://issues.jenkins-ci.org/browse/JENKINS-12787
Project: Jenkins
Issue Type: Bug
Components: gui
Affects Versions: current
Environment: Jenkins
Reporter: Joshua Davis
Priority: Blocker
Labels: gui, jenkins
After navigating to Manage-Configure System, the LOADING overlay never goes
away. It is impossible to save any configuration changes.
EXPECTED:
* You can save your global configuration.
Here is the stack trace from Chrome's JS console:
{code}
Uncaught TypeError: Object #Object has no method 'findMatchingInput'
(anonymous function)
e.targetUrl hudson-behavior.js:338
registerValidator hudson-behavior.js:343
apply behavior.js:73
(anonymous function) behavior.js:79
Behaviour.applySubtree behavior.js:68
Behaviour.applybehavior.js:54
(anonymous function)behavior.js:49
window.onload
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
