[JIRA] [subversion-plugin] (JENKINS-30293) Make Subversion plugin support Subversion 1.8
Title: Message Title Henri Gomez commented on JENKINS-30293 Re: Make Subversion plugin support Subversion 1.8 Ticket title shouldn't be "Make Subversion plugin support Subversion 1.9" ? 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] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Henri Gomez commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Same problem here : Jenkins 1.580.3 (hosted on linux) Windows 2012 R2 (as slave) 05:00:02 java.lang.IllegalStateException: Invalid object ID 136 iota=137 05:00:02 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:348) 05:00:02 at hudson.remoting.ExportTable.get(ExportTable.java:324) 05:00:02 at hudson.remoting.Channel.getExportedObject(Channel.java:604) 05:00:02 at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:311) 05:00:02 at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:295) 05:00:02 at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:254) 05:00:02 at hudson.remoting.UserRequest.perform(UserRequest.java:121) 05:00:02 at hudson.remoting.UserRequest.perform(UserRequest.java:49) 05:00:02 at hudson.remoting.Request$2.run(Request.java:324) 05:00:02 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) 05:00:02 at java.util.concurrent.FutureTask.run(FutureTask.java:262) 05:00:02 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 05:00:02 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 05:00:02 at java.lang.Thread.run(Thread.java:745) 05:00:02 at ..remote call to winslave04(Native Method) 05:00:02 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) 05:00:02 at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) 05:00:02 at hudson.remoting.Channel.call(Channel.java:752) 05:00:02 at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:173) 05:00:02 at com.sun.proxy.$Proxy71.join(Unknown Source) 05:00:02 at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:979) 05:00:02 at hudson.Launcher$ProcStarter.join(Launcher.java:388) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [virtualbox-plugin] (JENKINS-16231) Stop slave options should list all possible options, not just save and poweroff
Henri Gomez commented on JENKINS-16231 Stop slave options should list all possible options, not just save and poweroff What about PR, so I could review it and apply. Side note, I'm not using VB Plugin anymore. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-hook-plugin] (JENKINS-25267) Gitlab hook not building on merge request object
Henri Gomez commented on JENKINS-25267 Gitlab hook not building on merge request object Your fork ? https://github.com/javiplx/jenkins-gitlab-hook-plugin ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-hook-plugin] (JENKINS-25267) Gitlab hook not building on merge request object
Henri Gomez commented on JENKINS-25267 Gitlab hook not building on merge request object Basically, I want to mimic GitHub/CloudBees BuildHive feature. When a MR is adressed, job should be triggered with merged contents and results provided. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-hook-plugin] (JENKINS-25267) Gitlab hook not building on merge request object
Henri Gomez commented on JENKINS-25267 Gitlab hook not building on merge request object Well, I experimented a bit with gitlab plugin (https://github.com/jenkinsci/gitlab-plugin) and this plugin does the works (job triggered on MR). I'm now using gitlab plugin for post build on push and MR. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-hook-plugin] (JENKINS-25267) Gitlab hook not building on merge request object
Henri Gomez edited a comment on JENKINS-25267 Gitlab hook not building on merge request object Well, I experimented a bit with gitlab plugin (https://github.com/jenkinsci/gitlab-plugin) and this plugin does the works (job triggered on MR). I'm now using gitlab plugin for build on push and MR. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-hook-plugin] (JENKINS-25267) Gitlab hook not building on merge request object
Henri Gomez commented on JENKINS-25267 Gitlab hook not building on merge request object BTW, gitlab hook plugin could be usefull too. Do you consider some merge/share effort with gitlab plugin ? For newcomers, having different plugins for Gitlab could be a bit confusing This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-hook-plugin] (JENKINS-25267) Gitlab hook not building on merge request object
Henri Gomez commented on JENKINS-25267 Gitlab hook not building on merge request object Did there is a way with gitlab hook plugin to build on merge request (with contents to be merged) ? I playes with Gitlab Merge Request Plugin (https://github.com/jenkinsci/gitlab-merge-request-builder-plugin) but it seems no more maintened. I would be great to have its features included in Gitlab Hook. Any plan for ? 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Henri Gomez commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 @Darren I got errors even after cleaning workspace and using fresh copy. Subversion Plugin fetch contents in SVN 1.8 whereas I defined to use SVN 1.7. Some part of SVN operation respect 1.7 config but .svn is performed in 1.8 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Henri Gomez commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 Hi all, I updated today Subversion Plugin from 2.4.5 to 2.5 and got errors about old version : 0:00:34.350 Caused by: org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy at 00:00:34.350 '/var/lib/mycorp/cijenka/builder21/workspace/mirror-centos-repositories-ptx' (format '100'). 00:00:34.350 at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) 00:00:34.350 at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) 00:00:34.350 at org.tmatesoft.svn.core.internal.wc17.db.SVNWCDbRoot.init(SVNWCDbRoot.java:104) 00:00:34.350 at org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.init(SVNWCDb.java:242) 00:00:34.350 at org.tmatesoft.svn.core.internal.wc17.SVNWCContext.initWC(SVNWCContext.java:4979) 00:00:34.350 at org.tmatesoft.svn.core.internal.wc17.SVNWCContext.initializeWC(SVNWCContext.java:4928) 00:00:34.350 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.checkout(SvnNgAbstractUpdate.java:796) 00:00:34.350 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:26) 00:00:34.350 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:11) 00:00:34.350 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20) 00:00:34.350 at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) 00:00:34.350 at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1259) 00:00:34.350 at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) 00:00:34.350 at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:115) 00:00:34.350 at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:162) 00:00:34.350 at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:991) 00:00:34.350 at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:972) 00:00:34.350 at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:948) 00:00:34.350 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2577) 00:00:34.350 at hudson.remoting.UserRequest.perform(UserRequest.java:121) 00:00:34.350 at hudson.remoting.UserRequest.perform(UserRequest.java:49) 00:00:34.350 at hudson.remoting.Request$2.run(Request.java:324) 00:00:34.350 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) 00:00:34.350 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) 00:00:34.350 at java.util.concurrent.FutureTask.run(FutureTask.java:138) 00:00:34.350 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) 00:00:34.350 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) 00:00:34.350 at java.lang.Thread.run(Thread.java:662) Native Subversion is 1.8.x on master and slave (both openSUSE 13.1). I configured Subversion to use 1.7 format by default but it seems .svn has been created in 1.8 format. Is it normal ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Henri Gomez edited a comment on JENKINS-18935 Make Subversion plugin support Subversion 1.8 Hi all, I updated today Subversion Plugin from 2.4.5 to 2.5 and got errors about old version : 0:00:34.350 Caused by: org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy at 00:00:34.350 '/var/lib/mycorp/cijenka/builder21/workspace/mirror-centos-repositories-ptx' (format '100'). 00:00:34.350 at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) 00:00:34.350 at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) 00:00:34.350 at org.tmatesoft.svn.core.internal.wc17.db.SVNWCDbRoot.init(SVNWCDbRoot.java:104) 00:00:34.350 at org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.init(SVNWCDb.java:242) 00:00:34.350 at org.tmatesoft.svn.core.internal.wc17.SVNWCContext.initWC(SVNWCContext.java:4979) 00:00:34.350 at org.tmatesoft.svn.core.internal.wc17.SVNWCContext.initializeWC(SVNWCContext.java:4928) 00:00:34.350 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.checkout(SvnNgAbstractUpdate.java:796) 00:00:34.350 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:26) 00:00:34.350 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:11) 00:00:34.350 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20) 00:00:34.350 at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) 00:00:34.350 at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1259) 00:00:34.350 at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) 00:00:34.350 at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:115) 00:00:34.350 at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:162) 00:00:34.350 at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:991) 00:00:34.350 at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:972) 00:00:34.350 at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:948) 00:00:34.350 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2577) 00:00:34.350 at hudson.remoting.UserRequest.perform(UserRequest.java:121) 00:00:34.350 at hudson.remoting.UserRequest.perform(UserRequest.java:49) 00:00:34.350 at hudson.remoting.Request$2.run(Request.java:324) 00:00:34.350 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) 00:00:34.350 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) 00:00:34.350 at java.util.concurrent.FutureTask.run(FutureTask.java:138) 00:00:34.350 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) 00:00:34.350 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) 00:00:34.350 at java.lang.Thread.run(Thread.java:662) Native Subversion is 1.8.x on master and slave (both openSUSE 13.1). I configured Subversion to use 1.7 format by default but it seems .svn has been created in 1.8 format. Is it normal ? Reverting to Subversion Plugin 2.4.5 fixed problem. It seems plugin didn't follow subversion format settings. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ldap-plugin] (JENKINS-23214) LDAP Plugin occasionally does not connect LDAP server
Henri Gomez commented on JENKINS-23214 LDAP Plugin occasionally does not connect LDAP server Same error here on some Jenkins. All have exactly same configuration but some works and others don't works. And no log in catalina.out. Jenkins 1.562.2, LDAP plugin 1.10.2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins] (JENKINS-25125) Verbose log activate verbose for all Jenkins
Henri Gomez created JENKINS-25125 Verbose log activate verbose for all Jenkins Issue Type: Bug Assignee: Unassigned Components: dependency-check-jenkins Created: 13/Oct/14 3:33 PM Description: When selecting Enable verbose logging is Analysis part, verbose logging is activated for DC but also Jenkins core and plugins. It end up with javaX.log in jenkins home dir (and jenkins client). And log could be very huge Environment: Jenkins LTS 1.565.3 - DependencyCheck 1.2.4 Project: Jenkins Priority: Minor Reporter: Henri Gomez This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-23761) No route to host in scm access for multi-conf jobs
Henri Gomez created JENKINS-23761 No route to host in scm access for multi-conf jobs Issue Type: Bug Assignee: Unassigned Components: subversion Created: 11/Jul/14 4:17 PM Description: I get more and more random errors on multi-conf jobs where many slaves are triggered at same time to build native packages (freestyle). at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.checkout(SvnNgAbstractUpdate.java:706) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:14) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:9) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:777) at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:99) ... 14 more Caused by: svn: E175002: OPTIONS /svn/ecd-catalog/trunk/cifortify-sca failed at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:154) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:97) ... 34 more Caused by: org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS request failed on '/svn/ecd-catalog/trunk/cifortify-sca' svn: E175002: No route to host at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:777) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382) ... 33 more Caused by: svn: E175002: OPTIONS request failed on '/svn/ecd-catalog/trunk/cifortify-sca' at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:775) ... 34 more Caused by: svn: E175002: No route to host at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:109) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:528) ... 34 more Caused by: java.net.NoRouteToHostException: No route to host at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:529) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:570) at org.tmatesoft.svn.core.internal.util.SVNSocketConnection.run(SVNSocketConnection.java:57) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) ... 5 more Finished: FAILURE Of course host is up and accessible from slaves. I did svn checkout directly from slaves using native svn 1.7 without problems. Subversion server is using CollabNet 4.0.10 and SSL (using valid certificate). I tried various SVN operations (forcing checkout, update) but no more luck. This is a serious show stopper especially by its randomly nature, ie on 10 slaves, only one will be in trouble. Environment: Jenkins LTS 1.544.3, Subversion Plugin 2.4, CollabNet 4.0.10 (SSL) Project: Jenkins Priority: Major
[JIRA] [subversion] (JENKINS-23761) No route to host in scm access for multi-conf jobs
Henri Gomez updated JENKINS-23761 No route to host in scm access for multi-conf jobs Change By: Henri Gomez (11/Jul/14 4:18 PM) Affects Version/s: current Environment: JenkinsLTS1.544.3,SubversionPlugin2.4,CollabNet4.0.10(SSL) . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cluster-stats] (JENKINS-23712) Exceptions
Henri Gomez created JENKINS-23712 Exceptions Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: cluster-stats Created: 08/Jul/14 1:54 PM Description: I get more and more exception like this in Jenkins log : WARNING: RunListener failed java.lang.RuntimeException: Failed to serialize org.zeroturnaround.stats.ClusterStatisticsPlugin#statsData for class org.zeroturnaround.stats.ClusterStatisticsPlugin at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:214) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:182) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:167) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:108) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.TreeMarshaller.start(TreeMarshaller.java:82) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.marshal(AbstractTreeMarshallingStrategy.java:37) at com.thoughtworks.xstream.XStream.marshal(XStream.java:1026) at com.thoughtworks.xstream.XStream.marshal(XStream.java:1015) at com.thoughtworks.xstream.XStream.toXML(XStream.java:988) at hudson.XmlFile.write(XmlFile.java:178) at hudson.Plugin.save(Plugin.java:250) at org.zeroturnaround.stats.ClusterStatisticsPlugin.maybeSave(ClusterStatisticsPlugin.java:57) at org.zeroturnaround.stats.StartCompleteListener.onCompleted(StartCompleteListener.java:50) at hudson.model.listeners.RunListener.fireCompleted(RunListener.java:199) at hudson.model.Run.execute(Run.java:1735) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: java.lang.RuntimeException: Failed to serialize org.zeroturnaround.stats.model.StatsData#runStats for class org.zeroturnaround.stats.model.StatsData at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:214) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:182) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:167) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:108) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:223) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:210) ... 21 more Caused by: java.util.ConcurrentModificationException at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372) at java.util.AbstractList$Itr.next(AbstractList.java:343) at com.thoughtworks.xstream.converters.collections.CollectionConverter.marshal(CollectionConverter.java:73) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:223) at
[JIRA] [cluster-stats] (JENKINS-23712) Exceptions in multi-conf jobs and concurrents executions
Henri Gomez updated JENKINS-23712 Exceptions in multi-conf jobs and concurrents executions Change By: Henri Gomez (08/Jul/14 1:57 PM) Summary: Exceptions inmulti-confjobsandconcurrentsexecutions This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins] (JENKINS-23643) Regressions with 1.2.3
Henri Gomez commented on JENKINS-23643 Regressions with 1.2.3 Just installed 1.2.3.1 Build still fail when "Use Maven Artifacts as Scan Path" is selected : 00:04:03.707 [DependencyCheck] OWASP Dependency-Check Plugin v1.2.3.1 00:04:03.719 [DependencyCheck] Executing Dependency-Check analysis with the following options: 00:04:03.719 [DependencyCheck] -name = jenkins-v1-plugin 00:04:03.719 [DependencyCheck] -scanPath = ERROR - PATH NOT SPECIFIED OR INVALID. 00:04:03.719 [DependencyCheck] -outputDirectory = /var/lib/mycorp/cijenkins/jobs/jenkins-v1-plugin/workspace 00:04:03.719 [DependencyCheck] -dataDirectory = /var/lib/mycorp/cijenkins/jobs/jenkins-v1-plugin/workspace/dependency-check-data 00:04:03.719 [DependencyCheck] -verboseLogFile = /var/lib/mycorp/cijenkins/jobs/jenkins-v1-plugin/workspace/dependency-check.log 00:04:03.719 [DependencyCheck] -dataMirroringType = NIST CPE/CVE 00:04:03.719 [DependencyCheck] -cveUrl12Modified = http://swf-storage.lab1.lab.ptx.mycorp.int/downloads/nist/nvdcve-modified.xml 00:04:03.719 [DependencyCheck] -cveUrl20Modified = http://swf-storage.lab1.lab.ptx.mycorp.int/downloads/nist/nvdcve-2.0-modified.xml 00:04:03.719 [DependencyCheck] -cveUrl12Base = http://swf-storage.lab1.lab.ptx.mycorp.int/downloads/nist/nvdcve-%d.xml 00:04:03.719 [DependencyCheck] -cveUrl20Base = http://swf-storage.lab1.lab.ptx.mycorp.int/downloads/nist/nvdcve-2.0-%d.xml 00:04:03.719 [DependencyCheck] -useMavenArtifactsScanPath = true 00:04:03.719 [DependencyCheck] -jarAnalyzerEnabled = true 00:04:03.719 [DependencyCheck] -_javascript_AnalyzerEnabled = true 00:04:03.719 [DependencyCheck] -archiveAnalyzerEnabled = true 00:04:03.719 [DependencyCheck] -assemblyAnalyzerEnabled = true 00:04:03.719 [DependencyCheck] -nuspecAnalyzerEnabled = true 00:04:03.719 [DependencyCheck] -nexusAnalyzerEnabled = false 00:04:03.719 [DependencyCheck] -showEvidence = false 00:04:03.719 [DependencyCheck] -format = XML 00:04:03.719 [DependencyCheck] -autoUpdate = true 00:04:03.719 [DependencyCheck] The scan path(s) specified are not valid. Please specify a valid path to scan. 00:04:03.720 Build step 'Invoke OWASP Dependency-Check analysis' marked build as failure 00:04:03.802 [DependencyCheck] Skipping publisher since build result is FAILURE For second job, Maven job too, I could add DC in post-build but "Use Maven Artifacts as Scan Path" is not available anymore. Screenshot attached, and issue reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins] (JENKINS-23643) Regressions with 1.2.3
Henri Gomez reopened JENKINS-23643 Regressions with 1.2.3 1.2.3.1 didn't fix problems Change By: Henri Gomez (02/Jul/14 7:40 AM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins] (JENKINS-23643) Regressions with 1.2.3
Henri Gomez updated JENKINS-23643 Regressions with 1.2.3 Change By: Henri Gomez (02/Jul/14 7:40 AM) Attachment: Screenshot-20140702-093925.png Attachment: Screenshot-20140702-093904.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins] (JENKINS-23643) Regressions with 1.2.3
Henri Gomez edited a comment on JENKINS-23643 Regressions with 1.2.3 Just installed 1.2.3.1 Build still fail when "Use Maven Artifacts as Scan Path" is selected : 00:04:03.707 [DependencyCheck] OWASP Dependency-Check Plugin v1.2.3.1 00:04:03.719 [DependencyCheck] Executing Dependency-Check analysis with the following options: 00:04:03.719 [DependencyCheck] -name = jenkins-v1-plugin 00:04:03.719 [DependencyCheck] -scanPath = ERROR - PATH NOT SPECIFIED OR INVALID. 00:04:03.719 [DependencyCheck] -outputDirectory = /var/lib/mycorp/cijenkins/jobs/jenkins-v1-plugin/workspace 00:04:03.719 [DependencyCheck] -dataDirectory = /var/lib/mycorp/cijenkins/jobs/jenkins-v1-plugin/workspace/dependency-check-data 00:04:03.719 [DependencyCheck] -verboseLogFile = /var/lib/mycorp/cijenkins/jobs/jenkins-v1-plugin/workspace/dependency-check.log 00:04:03.719 [DependencyCheck] -dataMirroringType = NIST CPE/CVE 00:04:03.719 [DependencyCheck] -cveUrl12Modified = http://swf-storage.lab1.lab.ptx.mycorp.int/downloads/nist/nvdcve-modified.xml 00:04:03.719 [DependencyCheck] -cveUrl20Modified = http://swf-storage.lab1.lab.ptx.mycorp.int/downloads/nist/nvdcve-2.0-modified.xml 00:04:03.719 [DependencyCheck] -cveUrl12Base = http://swf-storage.lab1.lab.ptx.mycorp.int/downloads/nist/nvdcve-%d.xml 00:04:03.719 [DependencyCheck] -cveUrl20Base = http://swf-storage.lab1.lab.ptx.mycorp.int/downloads/nist/nvdcve-2.0-%d.xml 00:04:03.719 [DependencyCheck] -useMavenArtifactsScanPath = true 00:04:03.719 [DependencyCheck] -jarAnalyzerEnabled = true 00:04:03.719 [DependencyCheck] -_javascript_AnalyzerEnabled = true 00:04:03.719 [DependencyCheck] -archiveAnalyzerEnabled = true 00:04:03.719 [DependencyCheck] -assemblyAnalyzerEnabled = true 00:04:03.719 [DependencyCheck] -nuspecAnalyzerEnabled = true 00:04:03.719 [DependencyCheck] -nexusAnalyzerEnabled = false 00:04:03.719 [DependencyCheck] -showEvidence = false 00:04:03.719 [DependencyCheck] -format = XML 00:04:03.719 [DependencyCheck] -autoUpdate = true 00:04:03.719 [DependencyCheck] The scan path(s) specified are not valid. Please specify a valid path to scan. 00:04:03.720 Build step 'Invoke OWASP Dependency-Check analysis' marked build as failure 00:04:03.802 [DependencyCheck] Skipping publisher since build result is FAILURE For second job, Maven job too, I could add DC in post-build but "Use Maven Artifacts as Scan Path" is not available anymore. Screenshot attached, and issue reopened in post-step : in pre-step : This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins] (JENKINS-23643) Regressions with 1.2.3
Henri Gomez
commented on JENKINS-23643
Regressions with 1.2.3
I took a look at commit (https://github.com/hgomez/dependency-check-plugin/commit/9c29b7e321c192f9ac1a02d404f07d0b168ecfc7) and see some problems.
First, when you create post-pre step, instance didn't exist and so test for Maven is not executed :
j:if test="${instance.isMaven(it.getClass())}"
Also isMaven() in buildescriptor shouldn't use clazz but provided parm :
public boolean isMaven(Class? extends AbstractProject aP) {
return MavenModuleSet.class.isAssignableFrom(aP) || MavenModule.class.isAssignableFrom(aP);
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins] (JENKINS-23643) Regressions with 1.2.3
Henri Gomez
commented on JENKINS-23643
Regressions with 1.2.3
I noticed an error about missing artifacts.json :
java.io.FileNotFoundException: /var/lib/mycorp/cijenkins/jobs/svn-v1-hook/builds/2014-07-02_11-38-57/com.mycorp.v1link$v1link/archive/artifacts.json
There is artifacts.json in job workspace but not there and with another timestamp
/var/lib/mycorp/cijenkins/jobs/svn-v1-hook/modules/com.mycorp.rdops.connectors$svn-v1-hook/builds/2014-07-02_10-29-56/archive/artifacts.json
/var/lib/mycorp/cijenkins/jobs/svn-v1-hook/modules/com.mycorp.rdops.connectors$svn-v1-hook/builds/2014-07-02_11-39-03/archive/artifacts.json
/var/lib/mycorp/cijenkins/jobs/svn-v1-hook/modules/com.mycorp.rdops.connectors$svn-v1-hook/builds/2014-07-02_11-36-06/archive/artifacts.json
I took a look in artifacts.json, it seems empty :
{"@type":"java.util.LinkedHashSet"}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins] (JENKINS-23643) Regressions with 1.2.3
Henri Gomez
edited a comment on JENKINS-23643
Regressions with 1.2.3
I took a look at commit (https://github.com/jenkinsci/dependency-check-plugin/commit/9c29b7e321c192f9ac1a02d404f07d0b168ecfc7) and see some problems.
First, when you create post-pre step, instance didn't exist and so test for Maven is not executed :
j:if test="${instance.isMaven(it.getClass())}"
Also isMaven() in buildescriptor shouldn't use clazz but provided parm :
public boolean isMaven(Class? extends AbstractProject aP) {
return MavenModuleSet.class.isAssignableFrom(aP) || MavenModule.class.isAssignableFrom(aP);
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins] (JENKINS-23643) Regressions with 1.2.3
Henri Gomez commented on JENKINS-23643 Regressions with 1.2.3 I also reviewed artifacts.json generation and it won't works. Pom object passed in MavenArtifactRecorder is not real Maven pom but a Jenkins facade. pom.getArtifacts() didn't returns expected artifacts. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins] (JENKINS-23643) Regressions with 1.2.3
Henri Gomez created JENKINS-23643 Regressions with 1.2.3 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: dependency-check-jenkins Created: 01/Jul/14 4:40 PM Description: I upgraded a test instance from 1.2.1 to 1.2.3 One job add OWASP analysis registered but fail with : 00:01:07.264 [DependencyCheck] OWASP Dependency-Check Plugin v1.2.3 00:01:07.274 java.io.FileNotFoundException: /var/lib/mycorp/cijenkins/jobs/jenkins-v1-plugin/builds/2014-07-01_18-29-48/com.versionone$versionone-jenkins-notifier/archive/artifacts.json (No such file or directory) 00:01:07.276 [DependencyCheck] Executing Dependency-Check analysis with the following options: 00:01:07.276 [DependencyCheck] -name = jenkins-v1-plugin 00:01:07.276 [DependencyCheck] -scanPath = ERROR - PATH NOT SPECIFIED OR INVALID. 00:01:07.276 [DependencyCheck] -outputDirectory = /var/lib/mycorp/cijenkins/jobs/jenkins-v1-plugin/workspace 00:01:07.276 [DependencyCheck] -dataDirectory = /var/lib/mycorp/cijenkins/jobs/jenkins-v1-plugin/workspace/dependency-check-data 00:01:07.276 [DependencyCheck] -verboseLogFile = /var/lib/mycorp/cijenkins/jobs/jenkins-v1-plugin/workspace/dependency-check.log 00:01:07.276 [DependencyCheck] -dataMirroringType = NIST CPE/CVE 00:01:07.276 [DependencyCheck] -cveUrl12Modified = http://swf-storage.lab1.lab.ptx.mycorp.int/downloads/nist/nvdcve-modified.xml 00:01:07.276 [DependencyCheck] -cveUrl20Modified = http://swf-storage.lab1.lab.ptx.mycorp.int/downloads/nist/nvdcve-2.0-modified.xml 00:01:07.276 [DependencyCheck] -cveUrl12Base = http://swf-storage.lab1.lab.ptx.mycorp.int/downloads/nist/nvdcve-%d.xml 00:01:07.276 [DependencyCheck] -cveUrl20Base = http://swf-storage.lab1.lab.ptx.mycorp.int/downloads/nist/nvdcve-2.0-%d.xml 00:01:07.276 [DependencyCheck] -useMavenArtifactsScanPath = true 00:01:07.276 [DependencyCheck] -jarAnalyzerEnabled = true 00:01:07.276 [DependencyCheck] -_javascript_AnalyzerEnabled = true 00:01:07.276 [DependencyCheck] -archiveAnalyzerEnabled = true 00:01:07.276 [DependencyCheck] -assemblyAnalyzerEnabled = true 00:01:07.276 [DependencyCheck] -nuspecAnalyzerEnabled = true 00:01:07.276 [DependencyCheck] -nexusAnalyzerEnabled = false 00:01:07.276 [DependencyCheck] -showEvidence = false 00:01:07.276 [DependencyCheck] -format = XML 00:01:07.276 [DependencyCheck] -autoUpdate = false 00:01:07.277 [DependencyCheck] The scan path(s) specified are not valid. Please specify a valid path to scan. 00:01:07.277 Build step 'Invoke OWASP Dependency-Check analysis' marked build as failure 00:01:07.349 [DependencyCheck] Skipping publisher since build result is FAILURE 00:01:07.432 Sending e-mails to: hgo...@mycorp.com 00:01:08.090 Finished: FAILURE When I go to job configure Path to scan is grayed and not editable For a second job, I tried to add OWASP analysis in post-step, selected OWASP DC in menu but didn't get UI form. Same problem if I try with pre-step. No error reported in Tomcat logs I had to revert to 1.2.1 Environment: Jenkins LTS 1.544.2 / 1.544.3, Static Analyzer 1.57 Project: Jenkins Priority: Major Reporter: Henri Gomez 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
[JIRA] [dependency-check-jenkins] (JENKINS-23643) Regressions with 1.2.3
Henri Gomez commented on JENKINS-23643 Regressions with 1.2.3 It's when I select "Use Maven artifacts as scan path (experimental" that I got error about missing Scan Path. This control should be disabled in Maven mode This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins] (JENKINS-23643) Regressions with 1.2.3
Henri Gomez commented on JENKINS-23643 Regressions with 1.2.3 For UI, I did many tests but can get Dependency Check created. I double checked config.xml, nothing about org.jenkinsci.plugins.DependencyCheck.DependencyCheckBuilder has been registered in my job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-slaves] (JENKINS-23419) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected EOF
Henri Gomez commented on JENKINS-23419 FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected EOF I saw these errors also since we moved to 1.544.2 LTS. We didn't had these in 1.532.x LTS This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven2] (JENKINS-12843) Failure with maven 3 jobs and shade plugin
Henri Gomez commented on JENKINS-12843 Failure with maven 3 jobs and shade plugin I didn't get comment notification. Feel free to close it, so many things changed, Jenkins core, Jenkins Maven Plugin, Artifactory 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] [artifactory] (JENKINS-21832) Can't fetch remote repositories nor deploy
Henri Gomez created JENKINS-21832 Cant fetch remote repositories nor deploy Issue Type: Bug Affects Versions: current Assignee: yossis Components: artifactory Created: 17/Feb/14 2:26 PM Description: Since we updated our Artifactory Plugin from 2.1.8 to 2.2.1 on our Jenkins (LTS 1.532.1) we can't : Browse remote repositories in job Artifactory Deploy section We cannot deploy artifacts anymore We had to revert to 2.1.8 to get both works again Environment: Jenkins 1.532.1 LTS, Artifactory Plugin 2.2.1 Project: Jenkins Priority: Major Reporter: Henri Gomez 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] [artifactory] (JENKINS-21832) Can't fetch remote repositories nor deploy
Henri Gomez updated JENKINS-21832 Cant fetch remote repositories nor deploy Change By: Henri Gomez (17/Feb/14 2:50 PM) Environment: Jenkins1.532.1LTS,ArtifactoryPlugin2.2.1 ,Java1.6.0u45,Tocmat7.0.50 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] [artifactory] (JENKINS-21832) Can't fetch remote repositories nor deploy
Henri Gomez updated JENKINS-21832 Cant fetch remote repositories nor deploy Change By: Henri Gomez (17/Feb/14 2:50 PM) Environment: Jenkins1.532.1LTS,ArtifactoryPlugin2.2.1,Java1.6.0u45, Tocmat Tomcat 7.0.50 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] [dependency-check-jenkins] (JENKINS-21757) Make use of Maven dependencies inside DC plugin when executing a maven job
Henri Gomez created JENKINS-21757 Make use of Maven dependencies inside DC plugin when executing a maven job Issue Type: Bug Assignee: Unassigned Components: dependency-check-jenkins Created: 11/Feb/14 1:26 PM Description: Dependency Check Plugin run Dependency Check core and scan all workspace contents, including local maven repositories. This raise many false positive about vulnerabilities in artifacts not bundled in product but used in scope test, provided, runtime and even Maven plugins (ie Maven site using vulnerable Struts). Maven support is allready available in Dependency Check core and Jenkins integration in Dependency Check Plugin, this one should be able to use Jenkins/Maven integration fluently Project: Jenkins Priority: Major Reporter: Henri Gomez 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] [dependency-check-jenkins] (JENKINS-21758) Extra extensions should be scanned
Henri Gomez created JENKINS-21758 Extra extensions should be scanned Issue Type: Bug Assignee: Unassigned Components: dependency-check-jenkins Created: 11/Feb/14 1:29 PM Description: Dependency Check support a known set of file extensions to be scanner (zip, jar, war, ear, ...) For internal projects, customs extensions could be used and should be provided to DC via DC Jenkins Plugin. See https://github.com/jeremylong/DependencyCheck/issues/65 Project: Jenkins Priority: Major Reporter: Henri Gomez 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] [dependency-check-jenkins] (JENKINS-21758) Extra extensions should be scanned
Henri Gomez commented on JENKINS-21758 Extra extensions should be scanned In PR : https://github.com/jeremylong/DependencyCheck/pull/63 Sadly GitHub merged both PR ;( This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dependency-check-jenkins] (JENKINS-21732) Add an option to Skip DC Check on Upstream Changes
Henri Gomez updated JENKINS-21732 Add an option to Skip DC Check on Upstream Changes Change By: Henri Gomez (09/Feb/14 6:10 PM) Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dependency-check-jenkins] (JENKINS-21732) Add an option to Skip DC Check on Upstream Changes
Henri Gomez created JENKINS-21732 Add an option to Skip DC Check on Upstream Changes Issue Type: Bug Assignee: Unassigned Components: dependency-check-jenkins Created: 09/Feb/14 6:10 PM Description: With multi-modular Maven projects, we define jobs to be triggered by Snapshot Dependency changes. Adding Disable Check on such change to Dependency Check will avoid to have jobs triggered by any changes in related modules Project: Jenkins Priority: Major Reporter: Henri Gomez 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] [dependency-check-jenkins] (JENKINS-21732) Add an option to Skip DC Check on Upstream Changes
Henri Gomez commented on JENKINS-21732 Add an option to Skip DC Check on Upstream Changes Please take a look at this Pull-Request : https://github.com/jenkinsci/dependency-check-plugin/pull/1 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] [dependency-check-jenkins] (JENKINS-21732) Add an option to Skip DC Check on Upstream Changes
Henri Gomez commented on JENKINS-21732 Add an option to Skip DC Check on Upstream Changes Noticed you Steve merged it, good, I'll close this ticket 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] [dependency-check-jenkins] (JENKINS-21732) Add an option to Skip DC Check on Upstream Changes
Henri Gomez resolved JENKINS-21732 as Fixed Add an option to Skip DC Check on Upstream Changes Change By: Henri Gomez (09/Feb/14 6:11 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dependency-check-jenkins] (JENKINS-21732) Add an option to Skip DC Check on Upstream Changes
Henri Gomez edited a comment on JENKINS-21732 Add an option to Skip DC Check on Upstream Changes Noticed Steve merged it, good, I'll close this ticket 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] [dependency-check-jenkins] (JENKINS-20564) Analysis on Jenkins slave is 10/100 time slower than on Master
Henri Gomez closed JENKINS-20564 as Fixed Analysis on Jenkins slave is 10/100 time slower than on Master Change By: Henri Gomez (07/Feb/14 8:13 AM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dependency-check-jenkins] (JENKINS-20564) Analysis on Jenkins slave is 10/100 time slower than on Master
Henri Gomez commented on JENKINS-20564 Analysis on Jenkins slave is 10/100 time slower than on Master Guys, I'll close this ticket, this issue was solved in post 1.0.4.1 versions of plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dependency-check-jenkins] (JENKINS-20563) Data directory not working as expected
Henri Gomez closed JENKINS-20563 as Fixed Data directory not working as expected Change By: Henri Gomez (07/Feb/14 8:14 AM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dependency-check-jenkins] (JENKINS-20563) Data directory not working as expected
Henri Gomez commented on JENKINS-20563 Data directory not working as expected Problem has been fixed in 1.1.0, closing this ticket 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] [dependency-check-jenkins] (JENKINS-20564) Analysis on Jenkins slave is 10/100 time slower than on Master
Henri Gomez reopened JENKINS-20564 Analysis on Jenkins slave is 10/100 time slower than on Master Did a new test with 1.1.1, and sadly there is still a serious performance difference if job is performed on master or on slave Change By: Henri Gomez (07/Feb/14 8:53 AM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dependency-check-jenkins] (JENKINS-21708) Add an option to Skip DC Check on SCM Changes
Henri Gomez created JENKINS-21708 Add an option to Skip DC Check on SCM Changes Issue Type: Improvement Assignee: Unassigned Components: dependency-check-jenkins Created: 07/Feb/14 9:52 AM Description: We have tons of Jenkins jobs to be registered with Dependency Check. We don't want to slow down daily builds with analysis and would like to register DC check in our nightly analysis triggered by Sonar. It would be nice to an option in DC to avoid check if job was triggered by SCM Changes. This way will keep our daily jobs quick and have a nightly analysis including DC. Project: Jenkins Priority: Major Reporter: Henri Gomez 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] [dependency-check-jenkins] (JENKINS-21708) Add an option to Skip DC Check on SCM Changes
Henri Gomez commented on JENKINS-21708 Add an option to Skip DC Check on SCM Changes Hi Steve. I know about OWASP_DC_SKIP and this variable can be set/unset via parameters or EnvInject plugin but in this case, you'll end up with 2 set of Jenkins jobs. Nightly jobs, with OWASP_DC_SKIP set to FALSE and daily/on commit jobs with OWASP_DC_SKIP set to TRUE. It will turn to nighmare if you have hundred of CI jobs. Worst, developers may miss security issues because they track daily jobs and not nightly. We succeed to register a single set of job here, with Sonar activated by default BUT skipped on SCM commit (Sonar Plugin feature). Jobs are triggered by SCM change and nightly (via cron). By adding such option to DC Plugin to skip analysis on SCM change, DC be compatible with this nightly analysis approach and more easily registered in CI chains. 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] [dependency-check-jenkins] (JENKINS-21708) Add an option to Skip DC Check on SCM Changes
Henri Gomez edited a comment on JENKINS-21708 Add an option to Skip DC Check on SCM Changes Hi Steve. I know about OWASP_DC_SKIP and this variable can be set/unset via parameters or EnvInject plugin but in this case, you'll end up with 2 set of Jenkins jobs. Nightly jobs, with OWASP_DC_SKIP set to FALSE and daily/on commit jobs with OWASP_DC_SKIP set to TRUE. It will turn to nighmare if you have hundred of CI jobs. Worst, developers may miss security issues because they track daily jobs and not nightly. We succeed to register a single set of job here, with Sonar activated by default BUT skipped on SCM commit (Sonar Plugin feature). Jobs are triggered by SCM change and nightly (via cron). By adding such option to DC Plugin to skip analysis on SCM change, DC will be compatible with this nightly analysis approach and more easily registered in CI chains. 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] [artifactory] (JENKINS-20554) The version 2.2.1 of the Artifactory Plugin breaks all Maven 2 jobs
Henri Gomez commented on JENKINS-20554 The version 2.2.1 of the Artifactory Plugin breaks all Maven 2 jobs Same problem with Jenkins LTS 1.532.1. Reverted to 2.1.8 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] [slave-setup] (JENKINS-13869) [Unexpected termination of the channel] for Unix SSH slaves
Henri Gomez commented on JENKINS-13869 [Unexpected termination of the channel] for Unix SSH slaves It seems this issue has been fixed in Jenkins 1.536 : See JENKINS-18836, JENKINS-18879 and JENKINS-19619 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] [dependency-check-jenkins] (JENKINS-20564) Analysis on Jenkins slave is 10/100 time slower than on Master
Henri Gomez updated JENKINS-20564 Analysis on Jenkins slave is 10/100 time slower than on Master Change By: Henri Gomez (13/Nov/13 2:05 PM) Affects Version/s: current 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] [dependency-check-jenkins] (JENKINS-20564) Analysis on Jenkins slave is 10/100 time slower than on Master
Henri Gomez created JENKINS-20564 Analysis on Jenkins slave is 10/100 time slower than on Master Issue Type: Bug Assignee: Unassigned Attachments: on-master.log, on-slave.log Components: dependency-check-jenkins Created: 13/Nov/13 2:04 PM Description: Still evaluating latest DC (1.0.4.1). Same Java project Built on Jenkins Master : 20s Built on Jenkins Slave : 5mn Did there is some remote FS API involved ? If so, it's unneeded as build if performed on slaves and contents live on slaves Project: Jenkins Priority: Major Reporter: Henri Gomez 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] [dependency-check-jenkins] (JENKINS-20563) Data directory not working as expected
Henri Gomez created JENKINS-20563 Data directory not working as expected Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: dependency-check-jenkins Created: 13/Nov/13 1:26 PM Description: There is a problem with Dependency Check (1.4.0-1) and Data directory I defined Data directory to /var/lib/mycorp/cijenka/builder5/nist (aka inside builder agent storage) to ensure all jobs run on this Jenkins slave will use this shared CVE/CPE storage But DC data directory is not created under /var/lib/mycorp/cijenka/builder5/nist but as var/lib/mycorp/cijenka/builder5/nist in workspace ie: http://mysys/view/myprojects/job/myapp/ws/var/lib/mycorp/cijenka/builder5/nist/ ... [DependencyCheck] OWASP Dependency-Check Plugin v1.0.4.1 [DependencyCheck] Executing Dependency-Check analysis with the following options: [DependencyCheck] -name = dm_server_trunk-agent [DependencyCheck] -scanPath = /var/lib/mycorp/cijenka/builder5/workspace/dm_server_trunk-agent [DependencyCheck] -outputDirectory = /var/lib/mycorp/cijenka/builder5/workspace/dm_server_trunk-agent [DependencyCheck] -dataDirectory = /var/lib/mycorp/cijenka/builder5/workspace/dm_server_trunk-agent/var/lib/mycorp/cijenka/builder5/nist [DependencyCheck] -verboseLogFile = /var/lib/mycorp/cijenka/builder5/workspace/dm_server_trunk-agent/dependency-check.log [DependencyCheck] -dataMirroringType = NIST CPE/CVE [DependencyCheck] -cveUrl12Modified = http://swf-storage.lab1.lab.ptx.mycorp.int/downloads/nist/nvdcve-modified.xml [DependencyCheck] -cveUrl20Modified = http://swf-storage.lab1.lab.ptx.mycorp.int/downloads/nist/nvdcve-2.0-modified.xml [DependencyCheck] -cveUrl12Base = http://swf-storage.lab1.lab.ptx.mycorp.int/downloads/nist/ [DependencyCheck] -cveUrl20Base = http://swf-storage.lab1.lab.ptx.mycorp.int/downloads/nist/ [DependencyCheck] -showEvidence = false [DependencyCheck] -format = ALL [DependencyCheck] -autoUpdate = true [DependencyCheck] Scanning: /var/lib/mycorp/cijenka/builder5/workspace/dm_server_trunk-agent [DependencyCheck] Analyzing Dependencies Build is performed on a Jenkins Slave (Unix via SSH) and I get same error when running job on direct server itself Project: Jenkins Priority: Major Reporter: Henri Gomez 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] [all-changes] (JENKINS-18677) Some jobs not loaded after jenkins restart: java.lang.NoSuchFieldError: triggers
Henri Gomez commented on JENKINS-18677 Some jobs not loaded after jenkins restart: java.lang.NoSuchFieldError: triggers It's even worst for me. Fresh new Jenkins 1.522, I try to create a Maven 2/3 job : A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace javax.servlet.ServletException: java.lang.NoSuchFieldError: triggers at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:726) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:239) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:586) at org.kohsuke.stapler.Stapler.service(Stapler.java:217) at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) 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.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.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:48) 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 jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:118) 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
[JIRA] [all-changes] (JENKINS-18677) Some jobs not loaded after jenkins restart: java.lang.NoSuchFieldError: triggers
Henri Gomez commented on JENKINS-18677 Some jobs not loaded after jenkins restart: java.lang.NoSuchFieldError: triggers I reverted to 1.521 and problem disapears. And found 3 maven jobs installed some weeks ago on this instance ;( This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [all-changes] (JENKINS-18677) Some jobs not loaded after jenkins restart: java.lang.NoSuchFieldError: triggers
Henri Gomez commented on JENKINS-18677 Some jobs not loaded after jenkins restart: java.lang.NoSuchFieldError: triggers I tried to upgrade to 1.523 and Maven jobs can't be loaded at startup time ! SEVERE: Failed Loading job java.lang.NoSuchFieldError: triggers at hudson.maven.AbstractMavenProject.createTransientActions(AbstractMavenProject.java:187) at hudson.maven.MavenModuleSet.createTransientActions(MavenModuleSet.java:454) at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:724) at hudson.maven.MavenModuleSet.updateTransientActions(MavenModuleSet.java:450) at hudson.model.AbstractProject.onLoad(AbstractProject.java:322) at hudson.maven.MavenModuleSet.onLoad(MavenModuleSet.java:752) at hudson.model.Items.load(Items.java:221) at jenkins.model.Jenkins$18.run(Jenkins.java:2553) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:895) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:662) Jul 23, 2013 5:09:18 PM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading job dm_commons_trunk java.lang.NoSuchFieldError: triggers at hudson.maven.AbstractMavenProject.createTransientActions(AbstractMavenProject.java:187) at hudson.maven.MavenModuleSet.createTransientActions(MavenModuleSet.java:454) at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:724) at hudson.maven.MavenModuleSet.updateTransientActions(MavenModuleSet.java:450) at hudson.model.AbstractProject.onLoad(AbstractProject.java:322) at hudson.maven.MavenModuleSet.onLoad(MavenModuleSet.java:752) at hudson.model.Items.load(Items.java:221) at jenkins.model.Jenkins$18.run(Jenkins.java:2553) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:895) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:662) Jul 23, 2013 5:09:18 PM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading job dm_server_trunk java.lang.NoSuchFieldError: triggers at hudson.maven.AbstractMavenProject.createTransientActions(AbstractMavenProject.java:187) at hudson.maven.MavenModuleSet.createTransientActions(MavenModuleSet.java:454) at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:724) at hudson.maven.MavenModuleSet.updateTransientActions(MavenModuleSet.java:450) at hudson.model.AbstractProject.onLoad(AbstractProject.java:322) at hudson.maven.MavenModuleSet.onLoad(MavenModuleSet.java:752) at hudson.model.Items.load(Items.java:221) at jenkins.model.Jenkins$18.run(Jenkins.java:2553) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:895) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:662) Jul 23, 2013 5:09:18 PM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading job dm_connector_trunk java.lang.NoSuchFieldError: triggers at hudson.maven.AbstractMavenProject.createTransientActions(AbstractMavenProject.java:187) at hudson.maven.MavenModuleSet.createTransientActions(MavenModuleSet.java:454) at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:724) at hudson.maven.MavenModuleSet.updateTransientActions(MavenModuleSet.java:450) at hudson.model.AbstractProject.onLoad(AbstractProject.java:322) at hudson.maven.MavenModuleSet.onLoad(MavenModuleSet.java:752) at
[JIRA] [core] (JENKINS-17514) NullPointerException: no workspace from node hudson.slaves.DumbSlave after upgrade to 1.510
Henri Gomez commented on JENKINS-17514 NullPointerException: no workspace from node hudson.slaves.DumbSlave after upgrade to 1.510 Same problem on Windows slave : ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.com java.lang.NullPointerException: no workspace from node hudson.slaves.DumbSlave@19f89775 which is computer hudson.slaves.SlaveComputer@4c708d30 and has channel null at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:70) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:60) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:814) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.build(MavenModuleSetBuild.java:818) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:769) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:593) at hudson.model.Run.execute(Run.java:1568) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) project=hudson.maven.MavenModuleSet@3ab0f534[agent_win_trunk] project.getModules()=[hudson.maven.MavenModule@3b517b79[agent_win_trunk/com.mycorp.agent:agent-tests][agent_win_trunk/com.mycorp.agent:agent-tests][relativePath:], hudson.maven.MavenModule@24ce374a[agent_win_trunk/com.mycorp.agent:agent-tests-server][agent_win_trunk/com.mycorp.agent:agent-tests-server][relativePath:server], hudson.maven.MavenModule@7888dd83[agent_win_trunk/com.mycorp.agent:agent-tests-server-multihost][agent_win_trunk/com.mycorp.agent:agent-tests-server-multihost][relativePath:server/multihost], hudson.maven.MavenModule@42c31c7d[agent_win_trunk/com.mycorp.agent:agent-tests-server-singlehost][agent_win_trunk/com.mycorp.agent:agent-tests-server-singlehost][relativePath:server/singlehost]] project.getRootModule()=hudson.maven.MavenModule@3b517b79[agent_win_trunk/com.mycorp.agent:agent-tests][agent_win_trunk/com.mycorp.agent:agent-tests][relativePath:] FATAL: no workspace from node hudson.slaves.DumbSlave@19f89775 which is computer hudson.slaves.SlaveComputer@4c708d30 and has channel null java.lang.NullPointerException: no workspace from node hudson.slaves.DumbSlave@19f89775 which is computer hudson.slaves.SlaveComputer@4c708d30 and has channel null at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:70) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:60) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:814) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.build(MavenModuleSetBuild.java:818) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:769) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:593) at hudson.model.Run.execute(Run.java:1568) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17514) NullPointerException: no workspace from node hudson.slaves.DumbSlave after upgrade to 1.510
Henri Gomez edited a comment on JENKINS-17514 NullPointerException: no workspace from node hudson.slaves.DumbSlave after upgrade to 1.510 Same problem on Windows slave : Jenkins : 1.502 (Java 1.6.0-45) Windows Slave connected with JNLP (Java 1.6.0-37) ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.com java.lang.NullPointerException: no workspace from node hudson.slaves.DumbSlave@19f89775 which is computer hudson.slaves.SlaveComputer@4c708d30 and has channel null at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:70) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:60) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:814) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.build(MavenModuleSetBuild.java:818) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:769) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:593) at hudson.model.Run.execute(Run.java:1568) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) project=hudson.maven.MavenModuleSet@3ab0f534[agent_win_trunk] project.getModules()=[hudson.maven.MavenModule@3b517b79[agent_win_trunk/com.mycorp.agent:agent-tests][agent_win_trunk/com.mycorp.agent:agent-tests][relativePath:], hudson.maven.MavenModule@24ce374a[agent_win_trunk/com.mycorp.agent:agent-tests-server][agent_win_trunk/com.mycorp.agent:agent-tests-server][relativePath:server], hudson.maven.MavenModule@7888dd83[agent_win_trunk/com.mycorp.agent:agent-tests-server-multihost][agent_win_trunk/com.mycorp.agent:agent-tests-server-multihost][relativePath:server/multihost], hudson.maven.MavenModule@42c31c7d[agent_win_trunk/com.mycorp.agent:agent-tests-server-singlehost][agent_win_trunk/com.mycorp.agent:agent-tests-server-singlehost][relativePath:server/singlehost]] project.getRootModule()=hudson.maven.MavenModule@3b517b79[agent_win_trunk/com.mycorp.agent:agent-tests][agent_win_trunk/com.mycorp.agent:agent-tests][relativePath:] FATAL: no workspace from node hudson.slaves.DumbSlave@19f89775 which is computer hudson.slaves.SlaveComputer@4c708d30 and has channel null java.lang.NullPointerException: no workspace from node hudson.slaves.DumbSlave@19f89775 which is computer hudson.slaves.SlaveComputer@4c708d30 and has channel null at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:70) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:60) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:814) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.build(MavenModuleSetBuild.java:818) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:769) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:593) at hudson.model.Run.execute(Run.java:1568) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15156) Builds disappear from build history after completion
Henri Gomez assigned JENKINS-15156 to Jesse Glick Builds disappear from build history after completion Fix assignee Change By: Henri Gomez (06/Jun/13 11:03 AM) Assignee: VoiculescuBogdanAlexandru JesseGlick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18124) Modularize scm-sync-config scm implementations
Henri Gomez commented on JENKINS-18124 Modularize scm-sync-config scm implementations I don't have problem with many plugins, aka scm-sync-configuration-plugin scm-sync-configuration-plugin--impl. About SPOF, it will be nice to have SCM SYNC in Jenkins organisation, next to the core, since you experience issues when core moved. Currently it's a nightmare to have a working matrix in Jenkins, aka Core and Plugins aligned, and some sensible parts, like SCM SYNC should be part of core. My 0.01€ 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-17337) Failed to load job on Matrix jobs
Henri Gomez commented on JENKINS-17337 Failed to load job on Matrix jobs Same issue here, with all my Matrix jobs. Reverted to 1.506 to get them back 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-16867) Default ProcessTree should call any plugins to kill build
Henri Gomez commented on JENKINS-16867 Default ProcessTree should call any plugins to kill build Current code is available here : https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/util/ProcessTree.java More AIX informations about job controls should be provided to be able to propose a valid patch (pull-request) 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-16018) Not all builds show in the build history dashboard on job
Henri Gomez commented on JENKINS-16018 Not all builds show in the build history dashboard on job Same problem here with 1.498. 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-15156) Builds Disappear from Build History after Completion
Henri Gomez commented on JENKINS-15156 Builds Disappear from Build History after Completion Same problem here, with 1.498, under openSUSE Linux. I noticed this problem appears for jobs built on agents. 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-15156) Builds Disappear from Build History after Completion
Henri Gomez edited a comment on JENKINS-15156 Builds Disappear from Build History after Completion Same problem here, with 1.498 (powered by Tomcat 7.0.35) under openSUSE Linux. I noticed this problem appears for jobs built on agents. 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-15717) Failed to monitor warning
Henri Gomez commented on JENKINS-15717 Failed to monitor warning Any news about this one ? I'm using Jenkins 1.498, motorized by Tomcat 7.0.34, using Java 1.6.0-37 and I get : Jan 11, 2013 10:45:41 AM hudson.node_monitors.AbstractNodeMonitorDescriptor$Record run WARNING: Failed to monitor cdf-nexus-ptx for Free Swap Space java.io.InvalidClassException: hudson.node_monitors.SwapSpaceMonitor$MonitorTask; local class incompatible: stream classdesc serialVersionUID = 1, local class serialVersionUID = 1184166703664094906 at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:560) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1582) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1495) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1731) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1328) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350) at hudson.remoting.UserRequest.deserialize(UserRequest.java:182) at hudson.remoting.UserRequest.perform(UserRequest.java:98) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 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:662) 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-15717) Failed to monitor warning
Henri Gomez edited a comment on JENKINS-15717 Failed to monitor warning Any news about this one ? I'm using Jenkins 1.498, motorized by Tomcat 7.0.34, using Java 1.6.0-37. Slaves are controled by SSH and report as 2.20. Error reported : Jan 11, 2013 10:45:41 AM hudson.node_monitors.AbstractNodeMonitorDescriptor$Record run WARNING: Failed to monitor cdf-nexus-ptx for Free Swap Space java.io.InvalidClassException: hudson.node_monitors.SwapSpaceMonitor$MonitorTask; local class incompatible: stream classdesc serialVersionUID = 1, local class serialVersionUID = 1184166703664094906 at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:560) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1582) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1495) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1731) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1328) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350) at hudson.remoting.UserRequest.deserialize(UserRequest.java:182) at hudson.remoting.UserRequest.perform(UserRequest.java:98) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 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:662) 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-6721) Provide Link to VirtualBox Cloud Setup Documentation
Henri Gomez commented on JENKINS-6721 Provide Link to VirtualBox Cloud Setup Documentation What kind of documentation do you need ? VirtualBox plugin requires vboxwebdrv started and then Jenkins could use it ie : 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-6721) Provide Link to VirtualBox Cloud Setup Documentation
Henri Gomez updated JENKINS-6721 Provide Link to VirtualBox Cloud Setup Documentation Change By: Henri Gomez (14/Nov/12 6:44 PM) Attachment: VBP1.png 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-6721) Provide Link to VirtualBox Cloud Setup Documentation
Henri Gomez updated JENKINS-6721 Provide Link to VirtualBox Cloud Setup Documentation Change By: Henri Gomez (14/Nov/12 6:47 PM) Attachment: VBP2.png 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-6721) Provide Link to VirtualBox Cloud Setup Documentation
Henri Gomez edited a comment on JENKINS-6721 Provide Link to VirtualBox Cloud Setup Documentation What kind of documentation do you need ? VirtualBox plugin requires vboxwebdrv started and then Jenkins could use it. See attached screenshots 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-6721) Provide Link to VirtualBox Cloud Setup Documentation
Henri Gomez updated JENKINS-6721 Provide Link to VirtualBox Cloud Setup Documentation Change By: Henri Gomez (14/Nov/12 6:47 PM) Attachment: VBP3.png 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-15412) Jenkins not working with Java 8
Henri Gomez created JENKINS-15412 Jenkins not working with Java 8 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 05/Oct/12 7:29 AM Description: While trying Jenkins with Java 8 b59, I get following errors in catalina.out : Oct 05, 2012 9:22:44 AM org.kohsuke.stapler.jelly.AdjunctTag doTag WARNING: AdjunctManager is not installed for this application. Skipping adjunct tags java.lang.Exception at org.kohsuke.stapler.jelly.AdjunctTag.doTag(AdjunctTag.java:74) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:107) 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.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:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) 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) Connecting to Jenkins via browser and get this error also : AWT n'est pas configuré correctement sur ce serveur. Peut-être devez-vous lancer votre conteneur avec "-Djava.awt.headless=true"? java.lang.UnsatisfiedLinkError: sun.font.CFontManager.loadNativeDirFonts(Ljava/lang/String;)V at sun.font.CFontManager.loadNativeDirFonts(Native Method) at sun.font.CFontManager.registerFontsInDir(CFontManager.java:252) at sun.font.SunFontManager$2.run(SunFontManager.java:424) at java.security.AccessController.doPrivileged(Native Method) at sun.font.SunFontManager.init(SunFontManager.java:375) at sun.font.CFontManager.init(CFontManager.java:43) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:395) at java.lang.Class.newInstance0(Class.java:369) at java.lang.Class.newInstance(Class.java:321) at sun.font.FontManagerFactory$1.run(FontManagerFactory.java:83) at java.security.AccessController.doPrivileged(Native Method) at sun.font.FontManagerFactory.getInstance(FontManagerFactory.java:74) at java.awt.Font.getFont2D(Font.java:491) at java.awt.Font.getFamily(Font.java:1188) at
[JIRA] (JENKINS-15412) Jenkins not working with Java 8
Henri Gomez
updated JENKINS-15412
Jenkins not working with Java 8
Change By:
Henri Gomez
(05/Oct/12 7:33 AM)
Description:
WhiletryingJenkinswithJava8b59,Igetfollowingerrorsincatalina.out:{code}Oct05,20129:22:44AMorg.kohsuke.stapler.jelly.AdjunctTagdoTagWARNING:AdjunctManagerisnotinstalledforthisapplication.Skippingadjuncttagsjava.lang.Exceptionatorg.kohsuke.stapler.jelly.AdjunctTag.doTag(AdjunctTag.java:74)atorg.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)atorg.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)atorg.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)atorg.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)atorg.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)atorg.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)atorg.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81)atorg.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63)atorg.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53)atorg.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:107)atorg.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127)atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563)atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:659)atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:488)atorg.kohsuke.stapler.Stapler.service(Stapler.java:162)atjavax.servlet.http.HttpServlet.service(HttpServlet.java:722)atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210){code}ConnectingtoJenkinsviabrowserandgetthiserroralso:{code}AWTnestpasconfigurécorrectementsurceserveur.Peut-êtredevez-vouslancervotreconteneuravec-Djava.awt.headless=true?java.lang.UnsatisfiedLinkError:sun.font.CFontManager.loadNativeDirFonts(Ljava/lang/String;)V atsun.font.CFontManager.loadNativeDirFonts(NativeMethod) atsun.font.CFontManager.registerFontsInDir(CFontManager.java:252) atsun.font.SunFontManager$2.run(SunFontManager.java:424) atjava.security.AccessController.doPrivileged(NativeMethod) atsun.font.SunFontManager.init(SunFontManager.java:375) atsun.font.CFontManager.init(CFontManager.java:43) atsun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeMethod) atsun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) atsun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) atjava.lang.reflect.Constructor.newInstance(Constructor.java:395) atjava.lang.Class.newInstance0(Class.java:369) atjava.lang.Class.newInstance(Class.java:321) atsun.font.FontManagerFactory$1.run(FontManagerFactory.java:83) atjava.security.AccessController.doPrivileged(NativeMethod) atsun.font.FontManagerFactory.getInstance(FontManagerFactory.java:74) atjava.awt.Font.getFont2D(Font.java:491) atjava.awt.Font.getFamily(Font.java:1188) atjava.awt.Font.getFamily_NoClientCode(Font.java:1162) atjava.awt.Font.getFamily(Font.java:1154) atjava.awt.Font.toString(Font.java:1651) athudson.util.ChartUtil.clinit(ChartUtil.java:229) athudson.WebAppMain.contextInitialized(WebAppMain.java:172) atorg.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4791) atorg.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5285) atorg.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) atorg.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
[JIRA] (JENKINS-15260) Can't release VirtualBox Plugin
Henri Gomez commented on JENKINS-15260 Cant release VirtualBox Plugin I used Maven 3.0.4 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-15260) Can't release VirtualBox Plugin
Henri Gomez commented on JENKINS-15260 Cant release VirtualBox Plugin Olivier kindly provide help and fixed pom.xml https://github.com/jenkinsci/virtualbox-plugin/commit/d4771c1e16cfd99275d6194260bb093fee196bf6 https://github.com/jenkinsci/virtualbox-plugin/commit/c2eba8535b6d9dbdb8f8f5c1a3e7259982abd01c I also updated my settings.xml like this : settings xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd" interactiveModetrue/interactiveMode offlinefalse/offline servers server idmaven.jenkins-ci.org/id usernamehgomez/username passwordmyverysecretpassword/password /server /servers profiles profile idnormal/id activation activeByDefaulttrue/activeByDefault /activation repositories repository idrepo.jenkins-ci./id urlhttp://repo.jenkins-ci.org/public//url releases enabledtrue/enabled /releases snapshots enabledtrue/enabled /snapshots /repository /repositories pluginRepositories pluginRepository idrepo.jenkins-ci./id urlhttp://repo.jenkins-ci.org/public//url releases enabledtrue/enabled /releases snapshots enabledtrue/enabled /snapshots /pluginRepository /pluginRepositories /profile /profiles /settings 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-15260) Can't release VirtualBox Plugin
Henri Gomez resolved JENKINS-15260 as Fixed Cant release VirtualBox Plugin Change By: Henri Gomez (21/Sep/12 4:19 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-15260) Can't release VirtualBox Plugin
Henri Gomez updated JENKINS-15260 Cant release VirtualBox Plugin Change By: Henri Gomez (20/Sep/12 8:26 PM) Environment: MacOSX10.7.5,Maven3.0.4,Java1.6.0-35(64bits) 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-15260) Can't release VirtualBox Plugin
Henri Gomez created JENKINS-15260 Cant release VirtualBox Plugin Issue Type: Bug Assignee: Arnaud Héritier Components: virtualbox Created: 20/Sep/12 8:24 PM Description: While trying to release VirtualBox Plugin 0.5.0 I encountered this error : mbp-rico:virtualbox-plugin henri$ mvn3 -s ~/.m2/settings-std.xml -DdryRun=true release:prepare [INFO] Scanning for projects... [INFO] [INFO] Reactor Build Order: [INFO] [INFO] Jenkins VirtualBox Parent [INFO] Jenkins VirtualBox Plugin [INFO] Jenkins VirtualBox Client [INFO] [INFO] [INFO] Building Jenkins VirtualBox Parent 0.5-SNAPSHOT [INFO] [INFO] [INFO] --- maven-release-plugin:2.0:prepare (default-cli) @ virtualbox-parent --- [INFO] Verifying that there are no local modifications... [INFO] Executing: /bin/sh -c cd /Users/henri/Documents/gits/virtualbox-plugin git status [INFO] Working directory: /Users/henri/Documents/gits/virtualbox-plugin [INFO] Checking dependencies and plugins for snapshots ... What is the release version for "Jenkins VirtualBox Parent"? (org.jenkins-ci.plugins:virtualbox-parent) 0.5: : What is the release version for "Jenkins VirtualBox Plugin"? (org.jenkins-ci.plugins:virtualbox) 0.5: : What is the release version for "Jenkins VirtualBox Client"? (org.jenkins-ci.plugins:virtualbox-client) 0.5: : What is SCM release tag or label for "Jenkins VirtualBox Parent"? (org.jenkins-ci.plugins:virtualbox-parent) virtualbox-parent-0.5: : What is the new development version for "Jenkins VirtualBox Parent"? (org.jenkins-ci.plugins:virtualbox-parent) 0.6-SNAPSHOT: : What is the new development version for "Jenkins VirtualBox Plugin"? (org.jenkins-ci.plugins:virtualbox) 0.6-SNAPSHOT: : What is the new development version for "Jenkins VirtualBox Client"? (org.jenkins-ci.plugins:virtualbox-client) 0.6-SNAPSHOT: : [INFO] Transforming 'Jenkins VirtualBox Parent'... [WARNING] The POM for org.jenkins-ci.tools:maven-hpi-plugin:jar:1.64 is missing, no dependency information available [INFO] [INFO] Reactor Summary: [INFO] [INFO] Jenkins VirtualBox Parent . FAILURE [7.854s] [INFO] Jenkins VirtualBox Plugin . SKIPPED [INFO] Jenkins VirtualBox Client . SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 10.006s [INFO] Finished at: Thu Sep 20 22:21:14 CEST 2012 [INFO] Final Memory: 7M/81M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.0:prepare (default-cli) on project virtualbox-parent: Execution default-cli of goal org.apache.maven.plugins:maven-release-plugin:2.0:prepare failed: Failed to build parent project for org.jenkins-ci.plugins:virtualbox-parent:pom:0.5-SNAPSHOT: Some problems were encountered while processing the POMs: [ERROR] [ERROR] Unresolveable build extension: Plugin org.jenkins-ci.tools:maven-hpi-plugin:1.64 or one of its dependencies could not be resolved: Failure to find org.jenkins-ci.tools:maven-hpi-plugin:jar:1.64 in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced @: 1 problem was encountered while building the effective model for org.jenkins-ci.plugins:plugin:1.399 [ERROR] [ERROR] Unresolveable build extension: Plugin org.jenkins-ci.tools:maven-hpi-plugin:1.64 or one of its dependencies could not be resolved: Failure to find org.jenkins-ci.tools:maven-hpi-plugin:jar:1.64 in http://repo.maven.apache.org/maven2 was cached
[JIRA] (JENKINS-15175) VirtualBox 4.2.0 not supported
Henri Gomez resolved JENKINS-15175 as Fixed VirtualBox 4.2.0 not supported Fixed with pull-request : https://github.com/jenkinsci/virtualbox-plugin/pull/2 Will be available in 0.5.0 Change By: Henri Gomez (18/Sep/12 9:04 AM) Status: InProgress Resolved Assignee: godin HenriGomez 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-15175) VirtualBox 4.2.0 not supported
Henri Gomez created JENKINS-15175 VirtualBox 4.2.0 not supported Issue Type: Bug Assignee: godin Components: virtualbox Created: 15/Sep/12 6:20 AM Description: VirtualBox Plugin reports "VirtualBox version 4.2.0 not supported". Should it works with VB 4.2.x ? Project: Jenkins Priority: Major Reporter: Henri Gomez 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-15175) VirtualBox 4.2.0 not supported
Henri Gomez commented on JENKINS-15175 VirtualBox 4.2.0 not supported Worked on 4.2 Support and a pull-request is available : https://github.com/jenkinsci/virtualbox-plugin/pull/2 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-7408) Ability to specify the order of post build actions
[ https://issues.jenkins-ci.org/browse/JENKINS-7408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163652#comment-163652 ] Henri Gomez commented on JENKINS-7408: -- I was using 1.447 (LTS) and updated some instances to 1.465 and see it was fixed. Sorry for the noise Ability to specify the order of post build actions -- Key: JENKINS-7408 URL: https://issues.jenkins-ci.org/browse/JENKINS-7408 Project: Jenkins Issue Type: Improvement Components: core Affects Versions: current Environment: All Reporter: zankya Assignee: Kohsuke Kawaguchi Currently there is no way to specify the order in which the post build actions should get executed. It will be great to have ability to specify the order on the job configuration page (Just like how we can drag and drop the build steps in ay order that we want) The project configuration should then persist this order and execute the post build actions (such as JUnit result processing. PMD, FindBugs processing etc etc ) in that order. We want the trend graphs (for PMD, FindBugs, JUnit etc.) to be displayed in the order of their importance for the project. Currently it appears that the graphs are getting displayed in the order of their plugin names. -- 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-12843) Failure with maven 3 jobs and shade plugin
Henri Gomez created JENKINS-12843:
-
Summary: Failure with maven 3 jobs and shade plugin
Key: JENKINS-12843
URL: https://issues.jenkins-ci.org/browse/JENKINS-12843
Project: Jenkins
Issue Type: Bug
Components: maven2
Affects Versions: current
Environment: Jenkins 1.451, Sun/Oracle Java 1.6.0-31
Reporter: Henri Gomez
Attachments: company.zip, parent.zip, product.zip, settings-buggy.xml
A Maven project fail on Jenkins (in Maven job) whereas it works with Maven
3.0.3 in console or Maven 3.0.3 Job in freestyle.
This project use Maven Shade plugin and failed with Shade 1.3.2 and 1.5.
There is :
* a company pom (version 2)
* a parent pom (1.0.0-SNAPSHOT)
* a product pom (0.0.1-SNAPSHOT)
Artifacts stored on Artifactory OSS 2.5.0 :
* company pom
* parent pom
settings.xml attached :
If I use local repository for each job or if I remove org.mycorp artifacts from
shared repo before building product, build fail with :
{code}
[DEBUG] (f) outputDirectory =
/Users/henri/Documents/jenkins/data/jobs/test-product/workspace/target
[DEBUG] (f) project = MavenProject:
org.mycorp:product:0.0.1-SNAPSHOT @
/Users/henri/Documents/jenkins/data/jobs/test-product/workspace/pom.xml
[DEBUG] (f) promoteTransitiveDependencies = false
[DEBUG] (f) remoteArtifactRepositories = [ id: central
url: http://staging-darwin-ci.mycorp.org:12365/libs-release
layout: default
snapshots: [enabled = false, update = daily]
releases: [enabled = true, update = daily]
,id: snapshots
url: http://staging-darwin-ci.mycorp.org:12365/libs-snapshot
layout: default
snapshots: [enabled = true, update = daily]
releases: [enabled = true, update = daily]
]
[DEBUG] (f) shadedArtifactAttached = false
[DEBUG] (f) shadedArtifactId = product
[DEBUG] (f) shadedClassifierName = shaded
[DEBUG] -- end configuration --
[INFO] Including net.sourceforge.javacsv:javacsv:jar:2.0 in the shaded jar.
[INFO] Replacing original artifact with shaded artifact.
[INFO] Replacing
/Users/henri/Documents/jenkins/data/jobs/test-product/workspace/target/product-0.0.1-SNAPSHOT.jar
with
/Users/henri/Documents/jenkins/data/jobs/test-product/workspace/target/product-0.0.1-SNAPSHOT-shaded.jar
[DEBUG] Could not find metadata
org.mycorp:parent:1.0.0-SNAPSHOT/maven-metadata.xml in local
(/Users/henri/.m2/repository)
[DEBUG] Verifying availability of
/Users/henri/.m2/repository/org/mycorp/parent/1.0.0-SNAPSHOT/parent-1.0.0-SNAPSHOT.pom
from [central (http://repo1.maven.org/maven2, releases)]
[JENKINS] Archiving
/Users/henri/Documents/jenkins/data/jobs/test-product/workspace/pom.xml
to
/Users/henri/Documents/jenkins/data/jobs/test-product/modules/org.mycorp$product/builds/2012-02-21_11-00-44/archive/org.mycorp/product/0.0.1-SNAPSHOT/product-0.0.1-SNAPSHOT.pom
[JENKINS] Archiving
/Users/henri/Documents/jenkins/data/jobs/test-product/workspace/target/product-0.0.1-SNAPSHOT.jar
to
/Users/henri/Documents/jenkins/data/jobs/test-product/modules/org.mycorp$product/builds/2012-02-21_11-00-44/archive/org.mycorp/product/0.0.1-SNAPSHOT/product-0.0.1-SNAPSHOT.jar
[DEBUG] Could not find metadata
org.mycorp:parent:1.0.0-SNAPSHOT/maven-metadata.xml in local
(/Users/henri/.m2/repository)
[DEBUG] Intercepted metadata downloading event: METADATA_DOWNLOADING
org.mycorp:parent:1.0.0-SNAPSHOT/maven-metadata.xml @ snapshots
(http://staging-darwin-ci.mycorp.org:12365/libs-snapshot,
releases+snapshots)
[DEBUG] Enforcing repository URL: null for event: METADATA_DOWNLOADING
org.mycorp:parent:1.0.0-SNAPSHOT/maven-metadata.xml @ snapshots
(http://staging-darwin-ci.mycorp.org:12365/libs-snapshot,
releases+snapshots)
[DEBUG] Using connector WagonRepositoryConnector with priority 0 for
http://staging-darwin-ci.mycorp.org:12365/libs-snapshot
Downloading:
http://staging-darwin-ci.mycorp.org:12365/libs-snapshot/org/mycorp/parent/1.0.0-SNAPSHOT/maven-metadata.xml
Downloaded:
http://staging-darwin-ci.mycorp.org:12365/libs-snapshot/org/mycorp/parent/1.0.0-SNAPSHOT/maven-metadata.xml
(572 B at 37.2 KB/sec)
[DEBUG] Reading resolution tracking file
/Users/henri/.m2/repository/org/mycorp/parent/1.0.0-SNAPSHOT/resolver-status.properties
[DEBUG] Writing resolution tracking file
/Users/henri/.m2/repository/org/mycorp/parent/1.0.0-SNAPSHOT/resolver-status.properties
[DEBUG] Extension realms for project
org.mycorp:parent:pom:1.0.0-SNAPSHOT: (none)
[DEBUG] Looking up lifecyle mappings for packaging pom from
ClassRealm[plexus.core, parent: null]
[DEBUG] Extension realms for project org.mycorp:company:pom:2: (none)
[DEBUG] Looking up lifecyle mappings for packaging pom from
ClassRealm[plexus.core, parent: null]
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 5.750s
[INFO] Finished at: Tue Feb 21
[JIRA] (JENKINS-12843) Failure with maven 3 jobs and shade plugin
[
https://issues.jenkins-ci.org/browse/JENKINS-12843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Gomez updated JENKINS-12843:
--
Description:
A Maven project fail on Jenkins (in Maven job) whereas it works with Maven
3.0.3 in console or Maven 3.0.3 Job in freestyle.
This project use Maven Shade plugin and failed with Shade 1.3.2 and 1.5.
Similar to Shade Plugin error : https://jira.codehaus.org/browse/MSHADE-103
There is :
* a company pom (version 2)
* a parent pom (1.0.0-SNAPSHOT)
* a product pom (0.0.1-SNAPSHOT)
Artifacts stored on Artifactory OSS 2.5.0 :
* company pom
* parent pom
settings.xml attached :
If I use local repository for each job or if I remove org.mycorp artifacts from
shared repo before building product, build fail with :
{code}
[DEBUG] (f) outputDirectory =
/Users/henri/Documents/jenkins/data/jobs/test-product/workspace/target
[DEBUG] (f) project = MavenProject:
org.mycorp:product:0.0.1-SNAPSHOT @
/Users/henri/Documents/jenkins/data/jobs/test-product/workspace/pom.xml
[DEBUG] (f) promoteTransitiveDependencies = false
[DEBUG] (f) remoteArtifactRepositories = [ id: central
url: http://staging-darwin-ci.mycorp.org:12365/libs-release
layout: default
snapshots: [enabled = false, update = daily]
releases: [enabled = true, update = daily]
,id: snapshots
url: http://staging-darwin-ci.mycorp.org:12365/libs-snapshot
layout: default
snapshots: [enabled = true, update = daily]
releases: [enabled = true, update = daily]
]
[DEBUG] (f) shadedArtifactAttached = false
[DEBUG] (f) shadedArtifactId = product
[DEBUG] (f) shadedClassifierName = shaded
[DEBUG] -- end configuration --
[INFO] Including net.sourceforge.javacsv:javacsv:jar:2.0 in the shaded jar.
[INFO] Replacing original artifact with shaded artifact.
[INFO] Replacing
/Users/henri/Documents/jenkins/data/jobs/test-product/workspace/target/product-0.0.1-SNAPSHOT.jar
with
/Users/henri/Documents/jenkins/data/jobs/test-product/workspace/target/product-0.0.1-SNAPSHOT-shaded.jar
[DEBUG] Could not find metadata
org.mycorp:parent:1.0.0-SNAPSHOT/maven-metadata.xml in local
(/Users/henri/.m2/repository)
[DEBUG] Verifying availability of
/Users/henri/.m2/repository/org/mycorp/parent/1.0.0-SNAPSHOT/parent-1.0.0-SNAPSHOT.pom
from [central (http://repo1.maven.org/maven2, releases)]
[JENKINS] Archiving
/Users/henri/Documents/jenkins/data/jobs/test-product/workspace/pom.xml
to
/Users/henri/Documents/jenkins/data/jobs/test-product/modules/org.mycorp$product/builds/2012-02-21_11-00-44/archive/org.mycorp/product/0.0.1-SNAPSHOT/product-0.0.1-SNAPSHOT.pom
[JENKINS] Archiving
/Users/henri/Documents/jenkins/data/jobs/test-product/workspace/target/product-0.0.1-SNAPSHOT.jar
to
/Users/henri/Documents/jenkins/data/jobs/test-product/modules/org.mycorp$product/builds/2012-02-21_11-00-44/archive/org.mycorp/product/0.0.1-SNAPSHOT/product-0.0.1-SNAPSHOT.jar
[DEBUG] Could not find metadata
org.mycorp:parent:1.0.0-SNAPSHOT/maven-metadata.xml in local
(/Users/henri/.m2/repository)
[DEBUG] Intercepted metadata downloading event: METADATA_DOWNLOADING
org.mycorp:parent:1.0.0-SNAPSHOT/maven-metadata.xml @ snapshots
(http://staging-darwin-ci.mycorp.org:12365/libs-snapshot,
releases+snapshots)
[DEBUG] Enforcing repository URL: null for event: METADATA_DOWNLOADING
org.mycorp:parent:1.0.0-SNAPSHOT/maven-metadata.xml @ snapshots
(http://staging-darwin-ci.mycorp.org:12365/libs-snapshot,
releases+snapshots)
[DEBUG] Using connector WagonRepositoryConnector with priority 0 for
http://staging-darwin-ci.mycorp.org:12365/libs-snapshot
Downloading:
http://staging-darwin-ci.mycorp.org:12365/libs-snapshot/org/mycorp/parent/1.0.0-SNAPSHOT/maven-metadata.xml
Downloaded:
http://staging-darwin-ci.mycorp.org:12365/libs-snapshot/org/mycorp/parent/1.0.0-SNAPSHOT/maven-metadata.xml
(572 B at 37.2 KB/sec)
[DEBUG] Reading resolution tracking file
/Users/henri/.m2/repository/org/mycorp/parent/1.0.0-SNAPSHOT/resolver-status.properties
[DEBUG] Writing resolution tracking file
/Users/henri/.m2/repository/org/mycorp/parent/1.0.0-SNAPSHOT/resolver-status.properties
[DEBUG] Extension realms for project
org.mycorp:parent:pom:1.0.0-SNAPSHOT: (none)
[DEBUG] Looking up lifecyle mappings for packaging pom from
ClassRealm[plexus.core, parent: null]
[DEBUG] Extension realms for project org.mycorp:company:pom:2: (none)
[DEBUG] Looking up lifecyle mappings for packaging pom from
ClassRealm[plexus.core, parent: null]
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 5.750s
[INFO] Finished at: Tue Feb 21 11:00:53 CET 2012
[INFO] Final Memory: 11M/81M
[INFO]
[WARNING] The requested profile activateDarwinPlugin could not be
activated because it does not exist.
