[JIRA] (JENKINS-50339) log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update
Title: Message Title Oleg Nenashev commented on JENKINS-50339 Re: log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update GMC Software Development B Corporate The released patch will likely work in your case, please try it. If not, JENKINS-50237 in the next weekly should help as an ultimate power solution Best regards from Neuchâtel, Oleg Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50339) log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update
Title: Message Title GMC Software Development B Corporate commented on JENKINS-50339 Re: log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update Sorry for delayed response ... I've only found one SVNError-related stack-trace within a build-log on the same day; but time differs about 40 minutes (log-entry on master has the timestamp Mar 22, 2018 2:50:34 PM): Note: We are using timestamper-plugin to get/show local time within build-logs. [14:10:55] Checking out a fresh workspace because Jenkins failed to detect the current workspace E:\Jenkins\workspace\GMC_AdHocBuild [14:10:55] ERROR: svn: E155010: The node 'E:\Jenkins\workspace\GMC_AdHocBuild' was not found. [14:10:55] org.tmatesoft.svn.core.SVNException: svn: E155010: The node 'E:\Jenkins\workspace\GMC_AdHocBuild' was not found. [14:10:55] at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:70) [14:10:55] at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:57) [14:10:55] at org.tmatesoft.svn.core.internal.wc17.db.SvnWcDbConflicts.readConflictInternal(SvnWcDbConflicts.java:365) [14:10:55] at org.tmatesoft.svn.core.internal.wc17.db.SvnWcDbConflicts.readConflict(SvnWcDbConflicts.java:342) [14:10:55] at org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.readConflicts(SVNWCDb.java:3395) [14:10:55] at org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.readConflicts(SVNWCDb.java:3355) [14:10:55] at org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.opReadTreeConflict(SVNWCDb.java:2797) [14:10:55] at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgGetInfo.run(SvnNgGetInfo.java:74) [14:10:55] at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgGetInfo.run(SvnNgGetInfo.java:45) [14:10:55] at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20) [14:10:55] at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) [14:10:55] at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1239) [14:10:55] at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) [14:10:55] at org.tmatesoft.svn.core.wc.SVNWCClient.doInfo(SVNWCClient.java:2497) [14:10:55] at hudson.scm.subversion.UpdateUpdater$TaskImpl.parseSvnInfo(UpdateUpdater.java:126) [14:10:55] at hudson.scm.subversion.UpdateUpdater$TaskImpl.getSvnCommandToUse(UpdateUpdater.java:88) [14:10:55] at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:131) [14:10:55] at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:168) [14:10:55] at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:1030) [14:10:55] at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:1006) [14:10:55] at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:979) [14:10:55] at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2816) [14:10:55] at hudson.remoting.UserRequest.perform(UserRequest.java:207) [14:10:55] at hudson.remoting.UserRequest.perform(UserRequest.java:53) [14:10:55] at hudson.remoting.Request$2.run(Request.java:358) [14:10:55] at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) [14:10:55] at java.util.concurrent.FutureTask.run(Unknown Source) [14:10:55] at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [14:10:55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [14:10:55] at hudson.remoting.Engine$1$1.run(Engine.java:98) [14:10:55] at java.lang.Thread.run(Unknown Source) [14:10:55] Cleaning local Directory .
[JIRA] (JENKINS-50339) log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update
Title: Message Title Ivan Fernandez Calvo updated JENKINS-50339 it was released on 2.10.5 Jenkins / JENKINS-50339 log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update Change By: Ivan Fernandez Calvo Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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
[JIRA] (JENKINS-50339) log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50339 Re: log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update Code changed in jenkins User: Oleg Nenashev Path: Jenkinsfile http://jenkins-ci.org/commit/subversion-plugin/3d19e5788a28189aaa0b86bc9bc3d9da3054c6e3 Log: JENKINS-50339 - Jenkinsfile: Run CI on the LTS with JEP-200 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50339) log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50339 Re: log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update Code changed in jenkins User: Ivan Fernandez Calvo Path: Jenkinsfile pom.xml src/main/java/hudson/scm/CredentialsSVNAuthenticationProviderImpl.java src/main/java/hudson/scm/DirAwareSVNXMLLogHandler.java src/main/java/hudson/scm/SubversionEventHandlerImpl.java src/main/java/hudson/scm/SubversionSCM.java src/main/java/hudson/scm/subversion/SubversionUpdateEventHandler.java src/main/java/hudson/scm/subversion/UpdateWithCleanUpdater.java src/main/java/jenkins/scm/impl/subversion/RemotableSVNErrorMessage.java src/main/resources/META-INF/hudson.remoting.ClassFilter src/test/java/hudson/scm/SubversionSCMTest.java src/test/java/jenkins/scm/impl/subversion/RemotableSVNErrorMessageStepTest.java http://jenkins-ci.org/commit/subversion-plugin/5088b1cd54ed5107db46b9b09d2189b08f1728d2 Log: Merge pull request #211 from oleg-nenashev/bug/JENKINS-50339 JENKINS-50339 - Whitelist SVNErrorMessage and introduce RemotableSVNErrorMessage Compare: https://github.com/jenkinsci/subversion-plugin/compare/7f392ba32b36...5088b1cd54ed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50339) log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50339 Re: log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update Code changed in jenkins User: Oleg Nenashev Path: src/test/java/jenkins/scm/impl/subversion/RemotableSVNErrorMessageStepTest.java http://jenkins-ci.org/commit/subversion-plugin/23e1d059a52ed80bbe3a405306217551a11f5b8c Log: JENKINS-50339 - Add Unit test Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50339) log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50339 Re: log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update Code changed in jenkins User: Oleg Nenashev Path: pom.xml http://jenkins-ci.org/commit/subversion-plugin/20630b996bf3a721e8a34c52c1c07b0a9a1328cf Log: JENKINS-50339 - Update to the newest parent POM to support testing against 2.107.1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50339) log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50339 Re: log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update Code changed in jenkins User: Oleg Nenashev Path: src/main/java/jenkins/scm/impl/subversion/RemotableSVNErrorMessage.java http://jenkins-ci.org/commit/subversion-plugin/b420c0bf6eeceafde665c8753fd1a8032e917ce2 Log: JENKINS-50339 - RemotableSVNErrorMessage now uses proxy Exceptions for causes Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50339) log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50339 Re: log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update Code changed in jenkins User: Oleg Nenashev Path: src/main/resources/META-INF/hudson.remoting.ClassFilter http://jenkins-ci.org/commit/subversion-plugin/ab3b041f933588d1b6e748f2a3a0f635cc31918a Log: JENKINS-50339 - Whitelist ErrorMessage classes from SVNKit Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50339) log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50339 Re: log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update Code changed in jenkins User: Oleg Nenashev Path: src/main/java/hudson/scm/CredentialsSVNAuthenticationProviderImpl.java src/main/java/hudson/scm/DirAwareSVNXMLLogHandler.java src/main/java/hudson/scm/SubversionEventHandlerImpl.java src/main/java/hudson/scm/SubversionSCM.java src/main/java/hudson/scm/subversion/SubversionUpdateEventHandler.java src/main/java/hudson/scm/subversion/UpdateWithCleanUpdater.java src/main/java/jenkins/scm/impl/subversion/RemotableSVNErrorMessage.java src/test/java/hudson/scm/SubversionSCMTest.java http://jenkins-ci.org/commit/subversion-plugin/0b09aff1878bc67c5e4eaa2c6dca798780801ef5 Log: JENKINS-50339 - Introduce new RemotableSVNErrorMessage abstraction Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50339) log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update
Title: Message Title Oleg Nenashev updated JENKINS-50339 Jenkins / JENKINS-50339 log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update Change By: Oleg Nenashev Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50339) log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update
Title: Message Title Oleg Nenashev commented on JENKINS-50339 Re: log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update I have created https://github.com/jenkinsci/subversion-plugin/pull/211 which *should* fix the error. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50339) log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update
Title: Message Title
Oleg Nenashev commented on JENKINS-50339
Re: log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update
SVNErrorMessage is generally unsustainable due to Object fields:
public class SVNErrorMessage implements Serializable {
private static final long serialVersionUID = 4845L;
public static final int TYPE_ERROR = 0;
public static final int TYPE_WARNING = 1;
private Object[] myObjects;
private String myMessage;
private SVNErrorCode myErrorCode;
private int myType;
private SVNErrorMessage myChildErrorMessage;
private Throwable myThrowable;
private boolean dontShowErrorCode;
I will implement a proxy class
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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] (JENKINS-50339) log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update
Title: Message Title Oleg Nenashev started work on JENKINS-50339 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50339) log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update
Title: Message Title Oleg Nenashev commented on JENKINS-50339 Re: log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update The message class is widely used in error propagation, so some of the Remoting calls just throws it. Although I do not see which one without build logs, I think it's fine to just review it assuming that it is propagated within an exception. JENKINS-50237 should likely fix it anyway, but a temporary fix before the LTS with it would be helpful. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50339) log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update
Title: Message Title Jesse Glick commented on JENKINS-50339 Re: log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update From the description it sounds like there was no other stack trace visible. Any known way to reproduce from scratch? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50339) log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-50339 log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update Change By: Oleg Nenashev Assignee: Ivan Fernandez Calvo Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50339) log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update
Title: Message Title Oleg Nenashev commented on JENKINS-50339 Re: log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update GMC Software Development B Corporate would it be possible to get a full stacktrace? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50339) log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update
Title: Message Title
GMC Software Development B Corporate updated an issue
Jenkins / JENKINS-50339
log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update
Change By:
GMC Software Development B Corporate
Hi!I've found following log-entry, which may is JEP-200 relevant: { { quote} Mar 22, 2018 2:50:34 PM WARNING jenkins.security.ClassFilterImpl lambda$isBlacklisted$1org.tmatesoft.svn.core.SVNErrorMessage in [ file:/C:/xxx/Jenkins/plugins/subversion/WEB-INF/lib/svnkit-1.9.1.jar |file:///C:/xxx/Jenkins/plugins/subversion/WEB-INF/lib/svnkit-1.9.1.jar] might be dangerous, so rejecting; see [ https://jenkins.io/redirect/class-filter/ ]{quote } } Note: There are no other JEP-200 or subversion-related log-entries; also svn-checkout (in builds) were successfull.Best regards from Salzburg,Markus
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group
[JIRA] (JENKINS-50339) log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update
Title: Message Title
GMC Software Development B Corporate created an issue
Jenkins / JENKINS-50339
log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update
Issue Type:
Bug
Assignee:
Ivan Fernandez Calvo
Components:
subversion-plugin
Created:
2018-03-22 14:09
Environment:
Jenkins LTS 2.107.1 on Windows Server 2008 R2 x64, and Java(TM) SE Runtime Environment 1.8.0_161-b12 subversion-plugin (newest release) 2.10.4
Labels:
JEP-200
Priority:
Major
Reporter:
GMC Software Development B Corporate
Hi! I've found following log-entry, which may is JEP-200 relevant: {{Mar 22, 2018 2:50:34 PM WARNING jenkins.security.ClassFilterImpl lambda$isBlacklisted$1 org.tmatesoft.svn.core.SVNErrorMessage in file:/C:/xxx/Jenkins/plugins/subversion/WEB-INF/lib/svnkit-1.9.1.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/}} Note: There are no other JEP-200 or subversion-related log-entries; also svn-checkout (in builds) were successfull. Best regards from Salzburg, Markus
