[JIRA] [s3] (JENKINS-19725) Unable to unmarshall response (Couldn't initialize a SAX driver to create an XMLReader)
Tony Sweeney edited a comment on JENKINS-19725 Unable to unmarshall response (Couldn't initialize a SAX driver to create an XMLReader) Also an issue for us with Jenkins 1.543 and Jenkins S3 plugin version 0.5; seems to be a regression, as we definitely had this working before the last upgrade. Previous version was 1.521 and Jenkins S3 0.4; Not 100% this was working with that combo, I just know that it worked in the past. This message is automatically generated by JIRA. 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] [s3] (JENKINS-19725) Unable to unmarshall response (Couldn't initialize a SAX driver to create an XMLReader)
Tony Sweeney edited a comment on JENKINS-19725 Unable to unmarshall response (Couldn't initialize a SAX driver to create an XMLReader) Also an issue for us with Jenkins 1.543 and Jenkins S3 plugin version 0.5; seems to be a regression, as we definitely had this working before the last 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/groups/opt_out.
[JIRA] [s3] (JENKINS-19725) Unable to unmarshall response (Couldn't initialize a SAX driver to create an XMLReader)
Tony Sweeney commented on JENKINS-19725 Unable to unmarshall response (Couldn't initialize a SAX driver to create an XMLReader) Also an issue for us with Jenkins 1.543 and Jekins S3 plugin version 0.5; seems to be a regression, as we definitely had this working before the last 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/groups/opt_out.
[JIRA] [configurationslicing] (JENKINS-21556) Configuration slicing plugin throws UnsupportedOperationException when trying to change JDK for matrix build
Tony Sweeney commented on JENKINS-21556 Configuration slicing plugin throws UnsupportedOperationException when trying to change JDK for matrix build Note that it does actually change the on-disk setting in the config.xml for the JDK for the matrix build that causes the exception. However, it still shows as its original setting if you go back in to the JDK slicing plugin. It may be significant that I'm trying to change all builds that use the (Default) JDK to a different 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 -- 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] [configurationslicing] (JENKINS-21556) Configuration slicing plugin throws UnsupportedOperationException when trying to change JDK for matrix build
Tony Sweeney commented on JENKINS-21556 Configuration slicing plugin throws UnsupportedOperationException when trying to change JDK for matrix build It succeeds for builds that are alphabetically before the name of the offending matrix build. Given that Matrix builds have their own optional JDK build axis, it probably doesn't make much sense for the JDK slicing to even consider them as slicing candidates. This message is automatically generated by JIRA. 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] [configurationslicing] (JENKINS-21556) Configuration slicing plugin throws NPE when trying to change JDK for matrix build
Tony Sweeney commented on JENKINS-21556 Configuration slicing plugin throws NPE when trying to change JDK for matrix build javax.servlet.ServletException: java.lang.UnsupportedOperationException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) 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 net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:203) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:181) 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:99) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) 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:85) 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 org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) 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(Servle
[JIRA] [configurationslicing] (JENKINS-21556) Configuration slicing plugin throws UnsupportedOperationException when trying to change JDK for matrix build
Tony Sweeney updated JENKINS-21556 Configuration slicing plugin throws UnsupportedOperationException when trying to change JDK for matrix build Change By: Tony Sweeney (29/Jan/14 6:28 PM) Summary: Configuration slicing plugin throws NPE UnsupportedOperationException when trying to change JDK for matrix 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] [configurationslicing] (JENKINS-21556) Configuration slicing plugin throws NPE when trying to change JDK for matrix build
Tony Sweeney created JENKINS-21556 Configuration slicing plugin throws NPE when trying to change JDK for matrix build Issue Type: Bug Affects Versions: current Assignee: mdonohue Components: configurationslicing Created: 29/Jan/14 6:25 PM Description: If you try to use the configuration slicing plugin to change the JDK for a bunch of jobs using the default JDK to some other one, it throws a stack trace at the first matrix job that it encounters. This is true whether or not the JDK is one of the build axes for the job Environment: CentOS 5.9 master, assorted slaves Project: Jenkins Priority: Major Reporter: Tony Sweeney This message is automatically generated by JIRA. 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] [maven2] (JENKINS-21279) java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
Tony Sweeney edited a comment on JENKINS-21279 java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING OK, I had to fiddle a bit, as the delete dropdown menu item gave me a 403 bad crumb error, but if instead I selected the configure dropdown for the module, there was an option to delete the module in the left hand menu, which worked fine. If you then list the modules belonging to the build, the module still shows as present, but the status ball is greyed out. Running the build causes the module to be reinstantiated. This is a pretty painful workround, as I have many dozens of Maven builds each with a handful or two of modules. Worse, I can't actually validate it in my test system, since I can't reproduce the error there. But if it works it's better than nothing... This message is automatically generated by JIRA. 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] [maven2] (JENKINS-21279) java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
Tony Sweeney commented on JENKINS-21279 java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING OK, I had to fiddle a bit, as the delete dropdown menu item gave me a 403 bad crumb error, but if instead I selected the configure dropdown for the module, there was an option to delete the module in the left hand menu, which worked fine. If you then list the modules belonging to the build, the module still shows as present, but the status ball is greyed out. Running the build causes the module to be reinstantiated. This is a pretty painful workround, as I have many dozens of Maven builds each with a handful or two of modules. Worse, I can't actually validate it in my test system, since I can't reproduce the error there. This message is automatically generated by JIRA. 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] [maven2] (JENKINS-21279) java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
Tony Sweeney commented on JENKINS-21279 java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING I still don't understand what you mean by "deleting a module". Are you simply wiping the build slave workspace, or are you making a change to some of the build configuration? This message is automatically generated by JIRA. 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] [maven2] (JENKINS-21279) java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
Tony Sweeney commented on JENKINS-21279 java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING @Jeremy: I'm not sure I understand your workround. Could you be more precise about exactly what you did when "deleting all of the modules of the failing builds"? This message is automatically generated by JIRA. 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] [maven2] (JENKINS-21279) java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
Tony Sweeney edited a comment on JENKINS-21279 java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING Full list of plugins: [root@hudson0 plugins]# ls -1d *.?pi analysis-core.jpi ant.jpi audit-trail.jpi batch-task.jpi blame-upstream-commiters.hpi build-flow-plugin.jpi buildgraph-view.jpi build-name-setter.hpi build-pipeline-plugin.jpi build-user-vars-plugin.jpi cifs.hpi ci-game.hpi conditional-buildstep.jpi config-file-provider.jpi configurationslicing.jpi copyartifact.jpi credentials.jpi cvs.jpi dashboard-view.jpi description-setter.jpi disk-usage.jpi doxygen.jpi dry.jpi ec2.jpi email-ext.jpi emma.hpi envinject.jpi external-monitor-job.jpi findbugs.jpi ftppublisher.hpi git-client.jpi github-api.jpi github.jpi git.jpi greenballs.jpi htmlpublisher.jpi jacoco.jpi javadoc.jpi jenkins-cloudformation-plugin.jpi jenkins-multijob-plugin.jpi jira.jpi jquery.jpi ldap.jpi locks-and-latches.hpi m2release.jpi m2-repo-reaper.hpi mailer.jpi managed-scripts.jpi matrix-auth.jpi maven-plugin.jpi monitoring.jpi msbuild.jpi mstest.hpi multi-module-tests-publisher.jpi nant.hpi next-build-number.jpi node-iterator-api.jpi nunit.jpi pam-auth.jpi parameterized-trigger.jpi performance.hpi phing.jpi plot.hpi pmd.jpi port-allocator.jpi promoted-builds.jpi python.hpi release.jpi repository-connector.hpi run-condition.jpi s3.jpi scm-api.jpi scm-sync-configuration.jpi scons.hpi scp.hpi sectioned-view.jpi shelve-project-plugin.jpi slave-status.hpi sonar.jpi ssh-credentials.jpi ssh-slaves.jpi subversion.jpi svn-release-mgr.hpi svn-tag.hpi testflight.jpi testInProgress.jpi testng-plugin.jpi text-finder.hpi throttle-concurrents.jpi timestamper.jpi token-macro.jpi translation.jpi url-change-trigger.hpi URLSCM.hpi urltrigger.jpi violations.hpi ws-cleanup.jpi xunit.jpi zentimestamp.jpi [root@hudson0 plugins]# This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [maven2] (JENKINS-21279) java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
Tony Sweeney commented on JENKINS-21279 java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING Interestingly, I can't reproduce this on my test Jenkins instance, despite running the same versions of everything. This message is automatically generated by JIRA. 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] [maven2] (JENKINS-21279) java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
Tony Sweeney edited a comment on JENKINS-21279 java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING Full list of plugins: {core} [root@hudson0 plugins]# ls -1d *.?pi analysis-core.jpi ant.jpi audit-trail.jpi batch-task.jpi blame-upstream-commiters.hpi build-flow-plugin.jpi buildgraph-view.jpi build-name-setter.hpi build-pipeline-plugin.jpi build-user-vars-plugin.jpi cifs.hpi ci-game.hpi conditional-buildstep.jpi config-file-provider.jpi configurationslicing.jpi copyartifact.jpi credentials.jpi cvs.jpi dashboard-view.jpi description-setter.jpi disk-usage.jpi doxygen.jpi dry.jpi ec2.jpi email-ext.jpi emma.hpi envinject.jpi external-monitor-job.jpi findbugs.jpi ftppublisher.hpi git-client.jpi github-api.jpi github.jpi git.jpi greenballs.jpi htmlpublisher.jpi jacoco.jpi javadoc.jpi jenkins-cloudformation-plugin.jpi jenkins-multijob-plugin.jpi jira.jpi jquery.jpi ldap.jpi locks-and-latches.hpi m2release.jpi m2-repo-reaper.hpi mailer.jpi managed-scripts.jpi matrix-auth.jpi maven-plugin.jpi monitoring.jpi msbuild.jpi mstest.hpi multi-module-tests-publisher.jpi nant.hpi next-build-number.jpi node-iterator-api.jpi nunit.jpi pam-auth.jpi parameterized-trigger.jpi performance.hpi phing.jpi plot.hpi pmd.jpi port-allocator.jpi promoted-builds.jpi python.hpi release.jpi repository-connector.hpi run-condition.jpi s3.jpi scm-api.jpi scm-sync-configuration.jpi scons.hpi scp.hpi sectioned-view.jpi shelve-project-plugin.jpi slave-status.hpi sonar.jpi ssh-credentials.jpi ssh-slaves.jpi subversion.jpi svn-release-mgr.hpi svn-tag.hpi testflight.jpi testInProgress.jpi testng-plugin.jpi text-finder.hpi throttle-concurrents.jpi timestamper.jpi token-macro.jpi translation.jpi url-change-trigger.hpi URLSCM.hpi urltrigger.jpi violations.hpi ws-cleanup.jpi xunit.jpi zentimestamp.jpi [root@hudson0 plugins]#{core} This message is automatically generated by JIRA. 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] [maven2] (JENKINS-21279) java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
Tony Sweeney commented on JENKINS-21279 java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING Full list of plugins: {core} [root@hudson0 plugins]# ls -d *.?pi analysis-core.jpi monitoring.jpi ant.jpimsbuild.jpi audit-trail.jpimstest.hpi batch-task.jpi multi-module-tests-publisher.jpi blame-upstream-commiters.hpi nant.hpi build-flow-plugin.jpi next-build-number.jpi buildgraph-view.jpinode-iterator-api.jpi build-name-setter.hpi nunit.jpi build-pipeline-plugin.jpi pam-auth.jpi build-user-vars-plugin.jpi parameterized-trigger.jpi cifs.hpi performance.hpi ci-game.hpiphing.jpi conditional-buildstep.jpi plot.hpi config-file-provider.jpi pmd.jpi configurationslicing.jpi port-allocator.jpi copyartifact.jpi promoted-builds.jpi credentials.jpipython.hpi cvs.jpirelease.jpi dashboard-view.jpi repository-connector.hpi description-setter.jpi run-condition.jpi disk-usage.jpi s3.jpi doxygen.jpiscm-api.jpi dry.jpiscm-sync-configuration.jpi ec2.jpiscons.hpi email-ext.jpi scp.hpi emma.hpi sectioned-view.jpi envinject.jpi shelve-project-plugin.jpi external-monitor-job.jpi slave-status.hpi findbugs.jpi sonar.jpi ftppublisher.hpi ssh-credentials.jpi git-client.jpi ssh-slaves.jpi github-api.jpi subversion.jpi github.jpi svn-release-mgr.hpi git.jpisvn-tag.hpi greenballs.jpi testflight.jpi htmlpublisher.jpi testInProgress.jpi jacoco.jpi testng-plugin.jpi javadoc.jpitext-finder.hpi jenkins-cloudformation-plugin.jpi throttle-concurrents.jpi jenkins-multijob-plugin.jpitimestamper.jpi jira.jpi token-macro.jpi jquery.jpi translation.jpi ldap.jpi url-change-trigger.hpi locks-and-latches.hpi URLSCM.hpi m2release.jpi urltrigger.jpi m2-repo-reaper.hpi violations.hpi mailer.jpi ws-cleanup.jpi managed-scripts.jpixunit.jpi matrix-auth.jpizentimestamp.jpi maven-plugin.jpi [root@hudson0 plugins]#{core} This message is automatically generated by JIRA. 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] [maven2] (JENKINS-21279) java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
Tony Sweeney updated JENKINS-21279 java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING I had to back out the plugin upgrade, it broke too many of my builds. Change By: Tony Sweeney (08/Jan/14 4:48 PM) Priority: Major Critical This message is automatically generated by JIRA. 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] [maven2] (JENKINS-21279) java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
Tony Sweeney commented on JENKINS-21279 java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING The build of this project blows up too: Started by user Tony Sweeney [EnvInject] - Loading node environment variables. Building remotely on hudson3 in workspace S:\Hudson\workspace\auth-api-trunk FATAL: Null value not allowed as an environment variable: POM_PACKAGING java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING at hudson.EnvVars.put(EnvVars.java:356) at hudson.maven.MavenModuleSetBuild.getEnvironment(MavenModuleSetBuild.java:194) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:781) at hudson.model.AbstractProject.checkout(AbstractProject.java:1414) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:561) at hudson.model.Run.execute(Run.java:1678) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) This message is automatically generated by JIRA. 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] [maven2] (JENKINS-21279) java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
Tony Sweeney edited a comment on JENKINS-21279 java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING There was also an error on the configure page for the build in question. I set a per-node environment variable POM_PACKING=pom on the master node, which fixes the stack trace above, but now I'm seeing this one instead: javax.servlet.ServletException: java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) 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 net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:203) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:181) 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:99) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) 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:91) 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 org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) 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.se
[JIRA] [maven2] (JENKINS-21279) java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
Tony Sweeney commented on JENKINS-21279 java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING There was also an error on the configure page for the build in question. I set a per-node environment variable POM_PACKING=pom on the master node, which fixes the stack trace above, but I'm also seeing this one: javax.servlet.ServletException: java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) 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 net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:203) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:181) 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:99) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) 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:91) 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 org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) 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.Chain
[JIRA] [maven2] (JENKINS-21279) java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
Tony Sweeney created JENKINS-21279 java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING Issue Type: Bug Assignee: Unassigned Components: maven2 Created: 08/Jan/14 4:07 PM Description: SEVERE: Failed to record SCM polling for hudson.maven.MavenModuleSet@1118b490[testing-parent-trunk] java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING at hudson.EnvVars.put(EnvVars.java:356) at hudson.maven.MavenModuleSetBuild.getEnvironment(MavenModuleSetBuild.java:194) at hudson.scm.SubversionSCM.compareRemoteRevisionWith(SubversionSCM.java:1235) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject._poll(AbstractProject.java:1584) at hudson.model.AbstractProject.poll(AbstractProject.java:1493) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:456) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:485) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Environment: CentoOS 5 Linux master, assorted slaves Project: Jenkins Priority: Major Reporter: Tony Sweeney This message is automatically generated by JIRA. 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] [maven] (JENKINS-18592) JDK jdk1.5.0_12 builds fail with java.lang.UnsupportedClassVersionError since upgrade to Jenkins 1.520
Tony Sweeney commented on JENKINS-18592 JDK jdk1.5.0_12 builds fail with java.lang.UnsupportedClassVersionError since upgrade to Jenkins 1.520 We see the same problem. None of our Java5 Maven builds work any longer. Some of the classes in the maven-plugin.hpi are Java6 format: [sweeney@hudson0 plugins]$ unzip -l -p maven-plugin.hpi 'WEB-INF/classes/hudson/maven/ProcessCache$GetSystemProperties.class' > xxx [sweeney@hudson0 plugins]$ file xxx xxx: compiled Java class data, version 50.0 [sweeney@hudson0 plugins]$ rm xxx [sweeney@hudson0 plugins]$ We have to have Java5 artefacts because the target J2EE container runs atop Java5. We can work round this by using the Java6 compiler and modifying the build to explicitly request Java5-compatible artefacts, but that means changing several dozen jobs. If Java5 is deprecated in this release I would have expected to see something in the changelog. This message is automatically generated by JIRA. 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.