[JIRA] (JENKINS-44307) svn: E175002: CRLF expected at end of chunk: -1/-1
Title: Message Title Markus Schlegel commented on JENKINS-44307 Re: svn: E175002: CRLF expected at end of chunk: -1/-1 Had the problem today again. Workaround was to restart the server. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-44307) svn: E175002: CRLF expected at end of chunk: -1/-1
Title: Message Title Markus Schlegel commented on JENKINS-44307 Re: svn: E175002: CRLF expected at end of chunk: -1/-1 Hmm, my exception seems not be the exactly same one: org.tmatesoft.svn.core.SVNException: svn: E175002: CRLF expected at end of chunk: -1/-1 svn: E175002: REPORT request failed on '/svn/myrepo/!svn/vcc/default' at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:112) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:96) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:765) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:352) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:340) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:910) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:363) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.java:1349) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:847) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.updateInternal(SvnNgAbstractUpdate.java:263) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.update(SvnNgAbstractUpdate.java:115) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.checkout(SvnNgAbstractUpdate.java:877) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:26) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:11) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1239) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at hudson.scm.subversion.CheckoutUpdater$SubversionUpdateTask.perform(CheckoutUpdater.java:133) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:168) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:176) at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:134) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:168) at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:1041) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:1017) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:990) at hudson.FilePath.act(FilePath.java:1076) at hudson.FilePath.act(FilePath.java:1059) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:937) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:864) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Exec
[JIRA] (JENKINS-44307) svn: E175002: CRLF expected at end of chunk: -1/-1
Title: Message Title Markus Schlegel commented on JENKINS-44307 Re: svn: E175002: CRLF expected at end of chunk: -1/-1 Having this exception here too. Do you have a workaround? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-42610) NPE during pipeline execution in test-stability-plugin
Title: Message Title Markus Schlegel created an issue Jenkins / JENKINS-42610 NPE during pipeline execution in test-stability-plugin Issue Type: Bug Assignee: kutzi Components: test-stability-plugin Created: 2017/Mar/09 9:42 AM Environment: WIndows Server 2012R2, Java 64 bit 1.7.0_67, Jenkins 2.49 (running directly as service), test-stability-plugin V2.2, every plugin up-to-date. Priority: Major Reporter: Markus Schlegel While executing our pipeline job, we get this Exception: java.lang.NullPointerException at de.esailors.jenkins.teststability.StabilityTestDataPublisher.buildUpInitialHistory(StabilityTestDataPublisher.java:148) at de.esailors.jenkins.teststability.StabilityTestDataPublisher.contributeTestData(StabilityTestDataPublisher.java:101) at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:183) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:78) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:65) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:49) at hudson.security.ACL.impersonate(ACL.java:260) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:46) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:
[JIRA] [dependency-check-jenkins-plugin] (JENKINS-32279) OWASP Dependency-Check Plugin ignores supressions
Title: Message Title Markus Schlegel commented on JENKINS-32279 Re: OWASP Dependency-Check Plugin ignores supressions The suppressions are correctly handled when executing it from commandline: dependency-check.bat --project "TopEase" --scan "D:\DEV\TopEase\antbuild\PFiles" --scan "D:\DEV\TopEase\antbuild\PData" --suppression "D:\DEV\TopEase\source\OWASP-Dependency-Check-Suppression.xml" Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins-plugin] (JENKINS-32279) OWASP Dependency-Check Plugin ignores supressions
Title: Message Title Markus Schlegel updated an issue Jenkins / JENKINS-32279 OWASP Dependency-Check Plugin ignores supressions Change By: Markus Schlegel Attachment: configuration.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins-plugin] (JENKINS-32279) OWASP Dependency-Check Plugin ignores supressions
Title: Message Title Markus Schlegel updated an issue Jenkins / JENKINS-32279 OWASP Dependency-Check Plugin ignores supressions Our suppression file, where the content is ignored. Change By: Markus Schlegel Attachment: OWASP-Dependency-Check-Suppression.xml Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins-plugin] (JENKINS-32277) OWASP Dependency-Check Plugin's html-report is unusable
Title: Message Title Markus Schlegel commented on JENKINS-32277 Re: OWASP Dependency-Check Plugin's html-report is unusable Filed JENKINS-32296, thanks. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32296) Jenkins global security configuration page should provide option to configure the new "Content Security Policy"
Title: Message Title Markus Schlegel created an issue Jenkins / JENKINS-32296 Jenkins global security configuration page should provide option to configure the new "Content Security Policy" Issue Type: Improvement Assignee: Unassigned Components: core Created: 05/Jan/16 12:41 PM Environment: Jenkins 1.643 (with integrated webserver) Priority: Major Reporter: Markus Schlegel Filing this issue after discussion with Daniel Beck about JENKINS-32277. I appreciate the efforts to make Jenkins secure out of the box. But as Daniel pointed out already in his analysis in JENKINS-32026 : Good point. Unfortunately, while many, possibly most, Jenkins installations may not need this protection because it's not a threat to them... , the new CSP policy is relevant only for a minority of the Jenkins installations and breaks functionality which worked for years before. When I was searching for a workaround when discovered JENKINS-32277, one of the first things I made was looking for an option insi
[JIRA] [dependency-check-jenkins-plugin] (JENKINS-32277) OWASP Dependency-Check Plugin's html-report is unusable
Title: Message Title Markus Schlegel commented on JENKINS-32277 Re: OWASP Dependency-Check Plugin's html-report is unusable Thanks for the hint. Didn't realize, that this is caused by new security-flags of the jenkins server. When I first download the html report and then open it from the local disk, it works. I have read https://wiki.jenkins-ci.org/display/JENKINS/Configuring+Content+Security+Policy now and understand, that you made fundamental changes to how jenkins delivers files from the build result or from the workspace. As you've written, this makes many functionality unusable. I would have expected that such a fundamental change should be reflected in the security settings page of Jenkins (that's where I first looked for a setting before I filed the bug report). I am pretty sure, that there are MANY Jenkins installations which are solely accessible by the dev team members (and maybe other trusted users), where the CSP rule makes no sense at all. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins-plugin] (JENKINS-32279) OWASP Dependency-Check Plugin ignores supressions
Title: Message Title Markus Schlegel created an issue Jenkins / JENKINS-32279 OWASP Dependency-Check Plugin ignores supressions Issue Type: Bug Assignee: Unassigned Components: dependency-check-jenkins-plugin Created: 04/Jan/16 4:47 PM Environment: Jenkins-1.643, Windows, OWASP plugin 1.3.3 Priority: Minor Reporter: Markus Schlegel I have updated the OWASP dependency check plugin from version 1.3.1.2 to version 1.3.3 last week. Since the update, the plugin ignores the supressions which I have defined in the supressions file. Note, that unlike in JENKINS-30023 , it seems to find the supressions file correctly, at least as far as I can tell from the logfile: ... BUILD SUCCESSFUL Total time: 35 minutes 42 seconds [DependencyCheck] OWASP Dependency-Check Plugin v1.3.3 [DependencyCheck] Executing Dependency-Check with the following options: [DependencyCheck] -name = Trunk_BuildInstaller [DependencyCheck] -scanPath = C:\Jenkins\workspace\Trunk_BuildInstaller\TE\antbuild\PFiles [DependencyCheck] -scanPath = C:\Jenkins\workspace\Trunk_BuildInstaller\TE\antbuild\P
[JIRA] [dependency-check-jenkins-plugin] (JENKINS-32277) OWASP Dependency-Check Plugin's html-report is unusable
Title: Message Title Markus Schlegel created an issue Jenkins / JENKINS-32277 OWASP Dependency-Check Plugin's html-report is unusable Issue Type: Bug Assignee: Unassigned Components: dependency-check-jenkins-plugin Created: 04/Jan/16 4:34 PM Environment: Jenkins 1.643, Windows, OWASP plugin 1.3.3 Priority: Minor Reporter: Markus Schlegel Now, as generating the html report has been fixed, I can load the report in the browser, but it does not render well nor do the "suppress" buttons work. When I look at the console of the browser, there are plenty of error messages related to security issues (chrome & firefox). In IE, it seems to be somewhat better (no error message in the console), but even there the "suppress" buttons do not work at all. Add Comment
[JIRA] [dependency-check-jenkins-plugin] (JENKINS-30845) Exception while analyzing dependencies
Title: Message Title Markus Schlegel closed an issue as Fixed I can confirm, that this issue has been resolved. Successfully tested with 1.3.3. Jenkins / JENKINS-30845 Exception while analyzing dependencies Change By: Markus Schlegel Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins-plugin] (JENKINS-30023) OWASP Dependency-Check Plugin does not respect supressions anymore
Title: Message Title
Markus Schlegel edited a comment on JENKINS-30023
Re: OWASP Dependency-Check Plugin does not respect supressions anymore
Ok, I can confirm, that it works now, when specifying the path using {code} ${WORKSPACE} . {code} For everyone with the same problem: I had to change the suppression file path from " {code} TE/source/OWASP-Dependency-Check-Suppression.xml " {code} to " {code} ${WORKSPACE}\TE\source\OWASP-Dependency-Check-Suppression.xml ". {code} [~sspringett]: this single setting is the only one in my whole jenkins configuration where I ever had to use ${WORKSPACE}.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins-plugin] (JENKINS-30023) OWASP Dependency-Check Plugin does not respect supressions anymore
Title: Message Title
Markus Schlegel commented on JENKINS-30023
Re: OWASP Dependency-Check Plugin does not respect supressions anymore
Ok, I can confirm, that it works now, when specifying the path using $ {WORKSPACE}. For everyone with the same problem: I had to change the suppression file path from "TE/source/OWASP-Dependency-Check-Suppression.xml" to "${WORKSPACE}
\TE\source\OWASP-Dependency-Check-Suppression.xml".
Steve Springett: this single setting is the only one in my whole jenkins configuration where I ever had to use $ {WORKSPACE}
.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins-plugin] (JENKINS-30023) OWASP Dependency-Check Plugin does not respect supressions anymore
Title: Message Title Markus Schlegel commented on JENKINS-30023 Re: OWASP Dependency-Check Plugin does not respect supressions anymore I'll try that tomorrow. Just curious why it worked with 1.2.11.1 but not with 1.3.1.1 with the exact same settings... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins-plugin] (JENKINS-30023) OWASP Dependency-Check Plugin does not respect supressions anymore
Title: Message Title Markus Schlegel reopened an issue I tried it now again with the new version, but it still does not work. Log: [DependencyCheck] OWASP Dependency-Check Plugin v1.3.1.1 [DependencyCheck] Executing Dependency-Check with the following options: [DependencyCheck] -name = Trunk_BuildInstaller [DependencyCheck] -scanPath = C:\Jenkins\workspace\Trunk_BuildInstaller\TE\antbuild\PFiles [DependencyCheck] -scanPath = C:\Jenkins\workspace\Trunk_BuildInstaller\TE\antbuild\PData [DependencyCheck] -outputDirectory = C:\Jenkins\workspace\Trunk_BuildInstaller\TE\antbuild\test-reports\owasp [DependencyCheck] -dataDirectory = /owasp-dependency-check-data [DependencyCheck] -suppressionFile = TE/source/OWASP-Dependency-Check-Suppression.xml [DependencyCheck] -zipExtensions = war,zip [DependencyCheck] -dataMirroringType = none [DependencyCheck] -isQuickQueryTimestampEnabled = true [DependencyCheck] -useMavenArtifactsScanPath = false [DependencyCheck] -jarAnalyzerEnabled = true [DependencyCheck] -nodeJsAnalyzerEnabled = true [DependencyCheck] -composerLockAnalyzerEnabled = true [DependencyCheck] -pythonAnalyzerEnabled = true [DependencyCheck] -rubyGemAnalyzerEnabled = true [DependencyCheck] -archiveAnalyzerEnabled = true [DependencyCheck] -assemblyAnalyzerEnabled = true [DependencyCheck] -centralAnalyzerEnabled = true [DependencyCheck] -nuspecAnalyzerEnabled = true [DependencyCheck] -nexusAnalyzerEnabled = false [DependencyCheck] -autoconfAnalyzerEnabled = true [DependencyCheck] -cmakeAnalyzerEnabled = true [DependencyCheck] -opensslAnalyzerEnabled = true [DependencyCheck] -showEvidence = true [DependencyCheck] -format = XML [DependencyCheck] -autoUpdate = true [DependencyCheck] -updateOnly = false [DependencyCheck] WARNING: Suppression file does not exist. Omitting. The file DOES exist there. It worked the build before with version 1.2.11.1. I already tried to redefine the filepath in the configuration and also tried some variants. Note that the way you are building the file path now is different than before with version 1.2.11.1 Jenkins / JENKINS-30023 OWASP Dependency-Check Plugin does not respect supressions anymore Change By: Markus Schlegel Resolution: Fixed Status: Closed Reopened
[JIRA] [dependency-check-jenkins-plugin] (JENKINS-30845) Exception while analyzing dependencies
Title: Message Title Markus Schlegel commented on JENKINS-30845 Re: Exception while analyzing dependencies I'm not able to test this with 1.3.1 at the moment since I'd have to do this on our prod server and I know that JENKINS-30023 is still in there with 1.3.1 and breaks the builds. I will test this later, maybe when 1.3.2 with the fixed JENKINS-30023 is released. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins-plugin] (JENKINS-30845) Exception while analyzing dependencies
Title: Message Title Markus Schlegel commented on JENKINS-30845 Re: Exception while analyzing dependencies The problem appears only if I choose "Generate optional HTML reports" in the advanced options. This might have something to do with the newer Jenkins version 1.631 I use now (had 1.624 before). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins-plugin] (JENKINS-30845) Exception while analyzing dependencies
Title: Message Title Markus Schlegel created an issue Jenkins / JENKINS-30845 Exception while analyzing dependencies Issue Type: Bug Assignee: Unassigned Components: dependency-check-jenkins-plugin Created: 08/Oct/15 4:25 PM Environment: Windows 2012 32bit, Oracle Java 1.7.0_25, Jenkins 1.631, OWASP Dependency Check Plugin 1.2.11.1 Priority: Major Reporter: Markus Schlegel OWASP Dependency Check Plugin stopped working suddenly with the following Problem: [DependencyCheck] OWASP Dependency-Check Plugin v1.2.11.1 [DependencyCheck] Executing Dependency-Check with the following options: [DependencyCheck] -name = Trunk_BuildInstaller [DependencyCheck] -scanPath = C:\Jenkins\workspace\Trunk_BuildInstaller\TE\antbuild\PFiles [DependencyCheck] -scanPath = C:\Jenkins\workspace\Trunk_BuildInstaller\TE\antbuild\PData [DependencyCheck] -outputDirectory = C:\Jenkins\workspace\Trunk_BuildInstaller\TE\antbuild\test-reports\owasp [DependencyCheck] -dataDirectory = /owasp-dependency-check-data [DependencyCheck] -suppressionFile = C:\Jenkins\workspace\Trunk_BuildInstaller\TE\source\OWASP-Dependency-Check-Suppression.xml [DependencyCheck] -zipExtensions = war,zip [DependencyCheck] -dataMirroringType = no
[JIRA] [dependency-check-jenkins-plugin] (JENKINS-30023) OWASP Dependency-Check Plugin does not respect supressions anymore
Title: Message Title Markus Schlegel commented on JENKINS-30023 Re: OWASP Dependency-Check Plugin does not respect supressions anymore Hi Steve, I took time to look at the sourcecode to find the cause of this problem. It has been introduced in your commit "cf9df4dfa966d610816ea28f3ab221bfeea7edbc" from July 29 2015, where you have replaced the "FilePath" in the Options. In the method getSuppressionFilePath(), you simply replaced "FilePath" with "String". The implementation returns null if suppressionFile is not a String. Unfortunately, you did not change the callers of setSuppressionFile(Serializable). Also there is never any check about the valid class-type of that serializable object. Therefore, the outcome of getSuppressionFilePath() is in any case null since no caller actually puts a String into setSuppressionFile(Serializable). Since I do not know your intentions for the design of the Options class, I can not provide you with a pull request. I think it's best you fix this on your own. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins-plugin] (JENKINS-30023) OWASP Dependency-Check Plugin does not respect supressions anymore
Title: Message Title Markus Schlegel created an issue Jenkins / JENKINS-30023 OWASP Dependency-Check Plugin does not respect supressions anymore Issue Type: Bug Assignee: Unassigned Attachments: 2015-08-19_Trunk_BuildInstaller Config [Jenkins].png, 2015-08-19_Trunk_BuildInstaller [Jenkins]2.png, Dependency-Check Report.html, OWASP-Dependency-Check-Suppression.xml Components: dependency-check-jenkins-plugin Created: 19/Aug/15 9:12 AM Environment: Windows 2012 32bit, Oracle Java 1.7.0_25, Jenkins 1.6.24, OWASP Dependency Check Plugin 1.3.0 Labels: regression Priority: Major Reporter: Markus Schlegel After upgrading the OWASP Dependency Check Plugin to Version 1.3.0, all of my suppressions p
[JIRA] [jacoco] (JENKINS-23588) JaCoCo Plugin creates unreadable coverage report
Markus Schlegel updated JENKINS-23588 JaCoCo Plugin creates unreadable coverage report Guys, Attached two screenshots from the exactly same build. One that shows Emmas view to the code coverage metrics and another one showing Jacoco's view. The emma metrics have been built out of the Jacoco coverage result using an xslt stylesheet. As you can see (I hope you see it) the view given by emma is much more readable than jacoco's view. I would even say that Jacoco's views is completely unusable. Change By: Markus Schlegel (01/Oct/14 2:35 PM) Attachment: Jenkins-Emma.png Attachment: Jenkins-Jacoco.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] [jacoco] (JENKINS-19916) Confusing failure mode when no classes found by classPattern
Markus Schlegel commented on JENKINS-19916 Confusing failure mode when no classes found by classPattern It is not related to the reuse of the workspace. I changed the settings to let the job use it's own workspace and I get the same error. 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] [jacoco] (JENKINS-19916) Confusing failure mode when no classes found by classPattern
Markus Schlegel edited a comment on JENKINS-19916 Confusing failure mode when no classes found by classPattern I assume, I have the same problem here. I get the error: ... BUILD SUCCESSFUL Total time: 25 minutes 35 seconds Archiving artifacts Recording test results [JaCoCo plugin] Collecting JaCoCo coverage data... [JaCoCo plugin] antbuild/test-reports/*.exec;antbuild/all;source/java/**; locations are configured [JaCoCo plugin] Number of found exec files: 0 [JaCoCo plugin] Saving matched execfiles: [JaCoCo plugin] Saving matched class directories: [JaCoCo plugin] Saving matched source directories: [JaCoCo plugin] Loading inclusions files.. [JaCoCo plugin] inclusions: [] [JaCoCo plugin] exclusions: [**/*Test*.class] ERROR: Publisher hudson.plugins.jacoco.JacocoPublisher aborted due to exception java.lang.IllegalStateException: basedir C:\Jenkins\jobs\Trunk_TestCoverage\builds\2014-10-01_09-16-20\jacoco\classes does not exist at org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:550) at org.codehaus.plexus.util.FileUtils.getFileAndDirectoryNames(FileUtils.java:1717) at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1645) at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1627) at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1601) at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1584) at hudson.plugins.jacoco.ExecutionFileLoader.analyzeStructure(ExecutionFileLoader.java:128) at hudson.plugins.jacoco.ExecutionFileLoader.loadBundleCoverage(ExecutionFileLoader.java:137) at hudson.plugins.jacoco.JacocoReportDir.parse(JacocoReportDir.java:102) at hudson.plugins.jacoco.JacocoBuildAction.loadRatios(JacocoBuildAction.java:291) at hudson.plugins.jacoco.JacocoBuildAction.load(JacocoBuildAction.java:273) at hudson.plugins.jacoco.JacocoPublisher.perform(JacocoPublisher.java:371) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1770) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) after the build was otherwise successful. I am using the enhanced project's settings to reuse the workspace of a our main job. Maybe this is related to this kind of setup? 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] [jacoco] (JENKINS-19916) Confusing failure mode when no classes found by classPattern
Markus Schlegel commented on JENKINS-19916 Confusing failure mode when no classes found by classPattern I assume, I have the same problem here. I get the error: ERROR: Publisher hudson.plugins.jacoco.JacocoPublisher aborted due to exception java.lang.IllegalStateException: basedir C:\Jenkins\jobs\Trunk_TestCoverage\builds\2014-10-01_09-16-20\jacoco\classes does not exist at org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:550) at org.codehaus.plexus.util.FileUtils.getFileAndDirectoryNames(FileUtils.java:1717) at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1645) at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1627) at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1601) at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1584) at hudson.plugins.jacoco.ExecutionFileLoader.analyzeStructure(ExecutionFileLoader.java:128) at hudson.plugins.jacoco.ExecutionFileLoader.loadBundleCoverage(ExecutionFileLoader.java:137) at hudson.plugins.jacoco.JacocoReportDir.parse(JacocoReportDir.java:102) at hudson.plugins.jacoco.JacocoBuildAction.loadRatios(JacocoBuildAction.java:291) at hudson.plugins.jacoco.JacocoBuildAction.load(JacocoBuildAction.java:273) at hudson.plugins.jacoco.JacocoPublisher.perform(JacocoPublisher.java:371) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1770) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) after the build was otherwise successful. I am using the enhanced project's settings to reuse the workspace of a our main job. Maybe this is related to this kind of setup? 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] [thinBackup] (JENKINS-24302) backup ends before all jobs are backed-up if option "Backup build results" is switched on
Markus Schlegel commented on JENKINS-24302 backup ends before all jobs are backed-up if option "Backup build results" is switched on Windows Server 2008 R2 x64 Java 1.7.0_25, Apache Tomcat 6 Jenkins 1.565.1 thinBackup 1.7.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 -- 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] [thinBackup] (JENKINS-24302) backup ends before all jobs are backed-up if option "Backup build results" is switched on
Markus Schlegel updated JENKINS-24302 backup ends before all jobs are backed-up if option "Backup build results" is switched on The job's folder contains "shortcut" folders (see attached screenshot). Is this the problem? This is kind of normal for jenkins running on windows... Change By: Markus Schlegel (19/Aug/14 1:38 PM) Attachment: sf501.sf.jpg 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] [findbugs] (JENKINS-24289) Improve description of "Only use stable builds as reference" option
Markus Schlegel commented on JENKINS-24289 Improve description of "Only use stable builds as reference" option sounds great, 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] [thinBackup] (JENKINS-24302) backup ends before all jobs are backed-up if option "Backup build results" is switched on
Markus Schlegel created JENKINS-24302 backup ends before all jobs are backed-up if option "Backup build results" is switched on Issue Type: Bug Assignee: Thomas Fürer Attachments: Jenkins_2014-08-18_14-57-55.jpg Components: thinBackup Created: 18/Aug/14 12:59 PM Description: I am unable to backup my jenkins config using thinBackup as far as I enable the option "Backup build results". I only get one (very old and disabled) job backed up. All newer jobs do not appear in the backup folder. If I uncheck the option "Backup build results", it works (but of course without the build results). Project: Jenkins Priority: Critical Reporter: Markus Schlegel 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] [findbugs] (JENKINS-24289) FindBugs Plugin does not honor setting "Only use stable builds as reference" being off
Markus Schlegel commented on JENKINS-24289 FindBugs Plugin does not honor setting "Only use stable builds as reference" being off JENKINS-13458 is kind of what I was looking for, if specific to FindBugs (means setting the flag for findbugs does not set it for all others too). I voted for it. Maybe the tooltip on the flag "Only use stable builds as reference" could better reflect the current behavior. 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] [findbugs] (JENKINS-24289) FindBugs Plugin does not honor setting "Only use stable builds as reference" being off
Markus Schlegel commented on JENKINS-24289 FindBugs Plugin does not honor setting "Only use stable builds as reference" being off In the past few years, we had not set the threshold for the low priority issue. But due to a reorganisation, we now wanted to enable email notification for the developers which checked in also for these low-priority issues of Findbugs. Therefore we set the threshold such that every new low priority issue will result in an unstable build. So far so good. But sometimes, these low priority issues are just ok and we do not want the build be unstable forever. We would like that developers gain ONE email notification when the warning appeared the first time and not after every subsequent build. Therefore I thought that unchecking the setting "Only use stable builds as reference" should result in exactly that. Every subsequent build should calculate the number of new warnings from the last build (also from an unstable) and not the last stable one. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [findbugs] (JENKINS-24289) FindBugs Plugin does not honor setting "Only use stable builds as reference" being off
Markus Schlegel created JENKINS-24289 FindBugs Plugin does not honor setting "Only use stable builds as reference" being off Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Attachments: Trunk_BuildInstaller Config [Jenkins]_2014-08-15_16-54-12.jpg Components: findbugs Created: 15/Aug/14 2:56 PM Description: It seems to make no difference if "Only use stable builds as reference" is checked or not. The calculation of "new" warnigns always references the last stable build. Attached a screenshot which shows my config. Project: Jenkins Priority: Minor Reporter: Markus Schlegel 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] [build-environment] (JENKINS-24239) latest RC-Download available is still 1.565 from 20. May 2014. Latest release candidate is not available.
Markus Schlegel created JENKINS-24239 latest RC-Download available is still 1.565 from 20. May 2014. Latest release candidate is not available. Issue Type: Bug Assignee: Peter Hayes Components: build-environment, release Created: 13/Aug/14 6:10 AM Description: When I am on the RC download page (http://jenkins-ci.org/rc) and clicking a download link there (for example the windows download), I get the URL http://mirrors.jenkins-ci.org/war-rc/latest/jenkins.war The war currently provided by this link is V 1.565 from 20-May-2014 14:33 ! According to the Website, we should have 1.576 now. I tried various mirrors but could not find one which provides the actual RC release. Project: Jenkins Priority: Major Reporter: Markus Schlegel 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] (JENKINS-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39"
Markus Schlegel commented on JENKINS-15587 Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39" Same here, but the symlink-folders are not old ones, they have been created by the actual installed release, 1.488: Dec 19, 2012 7:46:19 AM hudson.model.RunMap retrieve WARNING: could not load D:\hudson_home\jobs\65_BuildInstaller\builds\4 hudson.util.IOException2: Invalid directory name D:\hudson_home\jobs\65_BuildInstaller\builds\4 at hudson.model.Run.parseTimestampFromBuildDir(Run.java:332) at hudson.model.Run.(Run.java:278) at hudson.model.AbstractBuild.(AbstractBuild.java:179) at hudson.model.Build.(Build.java:103) at hudson.model.FreeStyleBuild.(FreeStyleBuild.java:41) at sun.reflect.GeneratedConstructorAccessor426.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:525) at hudson.model.AbstractProject.loadBuild(AbstractProject.java:1061) at hudson.model.AbstractProject$1.create(AbstractProject.java:275) at hudson.model.AbstractProject$1.create(AbstractProject.java:273) at hudson.model.RunMap.retrieve(RunMap.java:220) at hudson.model.RunMap.retrieve(RunMap.java:59) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:638) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:601) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:344) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:502) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:355) at jenkins.model.lazy.AbstractLazyLoadRunMap.newestBuild(AbstractLazyLoadRunMap.java:297) at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:998) at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:137) at hudson.model.Job.getIconColor(Job.java:855) at hudson.model.AbstractProject.getIconColor(AbstractProject.java:654) at sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:72) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:58) 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.IncludeTag.doTag(IncludeTag.java:146) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) 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.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) 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.CoreTagLibra
[JIRA] (JENKINS-10835) Add support for JaCoCo coverage results
[ https://issues.jenkins-ci.org/browse/JENKINS-10835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163647#comment-163647 ] Markus Schlegel commented on JENKINS-10835: --- Hi Jose I do not know maven, and you did not provide the maven-config... I have the xslt still in use (with ant), the only thing I changed in the meantime is, that I use "BRANCH" instead of "COMPLEXITY" on line 102. > Add support for JaCoCo coverage results > --- > > Key: JENKINS-10835 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10835 > Project: Jenkins > Issue Type: New Feature > Components: emma >Reporter: Daniel Hirscher >Assignee: Kohsuke Kawaguchi > Attachments: jacoco_to_emma.xslt > > > JaCoCo is the successor of emma. > Maybe it is possible to support the new coverage file format. -- 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
