[JIRA] [dependency-check-jenkins-plugin] (JENKINS-30864) FilePath.writeObject() exception when saving configuration
Title: Message Title Victor Noël closed an issue as Cannot Reproduce I'm closing it, I think it was a problem on my side Jenkins / JENKINS-30864 FilePath.writeObject() exception when saving configuration Change By: Victor Noël Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins-plugin] (JENKINS-30023) OWASP Dependency-Check Plugin does not respect supressions anymore
Title: Message Title Victor Noël commented on JENKINS-30023 Re: OWASP Dependency-Check Plugin does not respect supressions anymore Hi, Could we still get variable resolution for URLs? According to current code, if it's a valid url but contains a variable in it, it won't be resolved… Thanks Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30431) Space in job name causes a spurious message from Maven
Title: Message Title Victor Noël commented on JENKINS-30431 Re: Space in job name causes a spurious message from Maven The trick will work, but I think it's a bit sad in 2015 to conclude that spaces in directories won't be handled Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30431) Space in job name causes a spurious message from Maven
Title: Message Title Victor Noël commented on JENKINS-30431 Re: Space in job name causes a spurious message from Maven Yep, just tried with maven 3.2.5 and the message is not present…not sure what it means. Also, the usual -B at the beginning of the mvn parameters is not present, contrary to the main maven goal for the build. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30431) Space in job name causes a spurious message from Maven
Title: Message Title Victor Noël commented on JENKINS-30431 Re: Space in job name causes a spurious message from Maven Note: I'm also using maven 3.3.3… Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30431) Space in job name causes a spurious message from Maven
Title: Message Title Victor Noël commented on JENKINS-30431 Re: Space in job name causes a spurious message from Maven Hi, I get the same message, but ONLY if I use a post-build maven step, in a maven project! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins-plugin] (JENKINS-30864) FilePath.writeObject() exception when saving configuration
Title: Message Title Victor Noël commented on JENKINS-30864 Re: FilePath.writeObject() exception when saving configuration No, I'm only using Linux, Java 7 and this version of jenkins which should be quite close to the LTS one. Maybe something shady happened... anyway, since you removed the use of FilePath for the suppression file in latest SNAPSHOT, this current bug doesn't mean anything any more, I think you can close it Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins-plugin] (JENKINS-30864) FilePath.writeObject() exception when saving configuration
Title: Message Title Victor Noël commented on JENKINS-30864 Re: FilePath.writeObject() exception when saving configuration I'm using: Jenkins version 1.611 (I'm stuck with it because we are using Maven jobs that needs Java 6 and they can't be run with Java 7 with the jenkins maven plugin). Dependency-Check Jenkins plugin version 1.3.1 (latest according to Jenkins). I tried different things: updating the configuration while a Dependency-Check job was running. then I cancelled the job because I thought it was linked but the error was still there. then on another job using Dependency-Check and that ended successfully, the bug manifested itself too. I think things started when I filled the suppressionFile field. Note also that if I just remove all the Dependency-Check configuration from the job configuration and save, the error appears too! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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...@googlegrou
[JIRA] [dependency-check-jenkins-plugin] (JENKINS-30865) Issues with the suppressionFile
Title: Message Title Victor Noël commented on JENKINS-30865 Re: Issues with the suppressionFile I'm wondering anyway if there is any reason to use a FilePath here: it's not as if it will be used remotely by Jenkins or the plugin… it is just used to be passed as an argument to dependency check… Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins-plugin] (JENKINS-30864) FilePath.writeObject() exception when saving configuration
Title: Message Title
Victor Noël updated an issue
Jenkins / JENKINS-30864
FilePath.writeObject() exception when saving configuration
Change By:
Victor Noël
Hi, When Once a job is running or has been cancelled running , its configuration can't be updated anymore, when doing so, the exception below is thrown.I suspect that the configuration stays attached to the slave's channel and thus the data can't be serialized anymore with FilePath…I had to restart jenkins for this to work again…{noformat}javax.servlet.ServletException: java.lang.RuntimeException: Failed to serialize hudson.maven.MavenModuleSet#postbuilders for class hudson.maven.MavenModuleSetat org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)at org.kohsuke.stapler.Stapler.service(Stapler.java:238)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:123)at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120)at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114)at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)at jenkins.security.Basi
[JIRA] [dependency-check-jenkins-plugin] (JENKINS-30865) Issues with the suppressionFile
Title: Message Title Victor Noël created an issue Jenkins / JENKINS-30865 Issues with the suppressionFile Issue Type: Bug Assignee: Unassigned Components: dependency-check-jenkins-plugin Created: 09/Oct/15 3:19 PM Priority: Minor Reporter: Victor Noël Hi, In the code of DependencyCheckBuilder, the suppression file is first set as an URL, then if it doesn't work it is set a a FilePath. If there is a variable in the field but it is an URL, the substitution doesn't seem to be applied… Then if it is set as a FilePath, strangely, in Option, the only way to get it, is as a String (see Options#getSuppressionFilePath() which returns a String and check if suppressionFile is an instance of String, which can never happen!). It makes suppression file impossible to work when it is used as a FilePath… the only workaround seems to use an URL of style file:/ but then I can't use a variable in it. Add Comment
[JIRA] [dependency-check-jenkins-plugin] (JENKINS-30864) FilePath.writeObject() exception when saving configuration
Title: Message Title Victor Noël created an issue Jenkins / JENKINS-30864 FilePath.writeObject() exception when saving configuration Issue Type: Bug Assignee: Unassigned Components: dependency-check-jenkins-plugin Created: 09/Oct/15 3:14 PM Priority: Minor Reporter: Victor Noël Hi, When a job is running or has been cancelled, its configuration can't be updated anymore, when doing so, the exception below is thrown. I suspect that the configuration stays attached to the slave's channel and thus the data can't be serialized anymore with FilePath… I had to restart jenkins for this to work again… javax.servlet.ServletException: java.lang.RuntimeException: Failed to serialize hudson.maven.MavenModuleSet#postbuilders for class hudson.maven.MavenModuleSet at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke
[JIRA] [core] (JENKINS-28120) Jenkins core to require Java7
Title: Message Title Victor Noël commented on JENKINS-28120 Re: Jenkins core to require Java7 Jesse, why would you strongly recommend to use the freestyle project type for Maven builds? I tried to look at it but there is two different build step available: invoke maven3 and invoke maven goal (or something like that, I am not using the english locale). Which one should then be used? And are dependencies taken into account to trigger the jobs as with the maven project type? Is there specific to do w.r.t. to the tests and the unstability of the build? Thank you for your help Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28368) Error "JDK 5 not supported to run Maven" while running Java 6
Title: Message Title Victor Noël commented on JENKINS-28368 Re: Error "JDK 5 not supported to run Maven" while running Java 6 I am wondering if it's not related to the fact that the maven31-agent.jar and co are compiled using Java 7 since Jenkins only support Java 7… but these artifacts should be able to support older version of Java even though Jenkins does not, no? Because it becomes impossible to use something else than Java 7 to execute jobs in Jenkins then… Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28368) Error "JDK 5 not supported to run Maven" while running Java 6
Title: Message Title Victor Noël created an issue Jenkins / JENKINS-28368 Error "JDK 5 not supported to run Maven" while running Java 6 Issue Type: Bug Assignee: Unassigned Components: core Created: 13/May/15 7:59 AM Priority: Major Reporter: Victor Noël Hi, I don't know why this problem appeared today, when running a job using Java 6, we got the following error: ERROR: JENKINS-18403 JDK 5 not supported to run Maven And then Jenkins switched to Java 7 (which we don't want). You can see the whole log here: http://jenkins.petalslink.com/view/81%20-%20Petals%20ESB%20Enterprise%204.3.x/job/4.3.x%20-%20Petals%20Components%20-%20CDK%20-%20Parent%20POM/2/console I checked the source code, and I guess a UnsupportedClassVersionError happened. It would maybe best to log the exception when it does to at least ease diagnostic if the problem is coming from us… but I don't think it is the case because it happens really at the beginning of the execution… Thanks!
[JIRA] [maven-plugin] (JENKINS-27930) Consider plugins's dependencies as triggers for building a maven project
Victor Noël created JENKINS-27930 Consider plugins's dependencies as triggers for building a maven project Issue Type: Improvement Assignee: Unassigned Components: maven-plugin Created: 14/Apr/15 1:32 PM Description: Hi, When using the option to trigger builds of jobs when one of its dependency has been rebuilt, the dependencies of the plugins are not used. For example I have one project A that uses the antrun maven plugin, and in the plugins dependency section we refer to project B. When a new SNAPSHOT version of project B is built, project A is not triggered for building as one would expect. Thank you Environment: maven 3.2.2 and jenkins 1.606 Project: Jenkins Priority: Major Reporter: Victor Noël This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
