dependency-check | checks which modules you have used in your code | JSON Processing library

You need Java 11 to build the project. I was able to build it locally using JDK 11. I used maven wrapper. You can try using the following command.

Above work was done on a feature branch. There was an error in the master branch. When trying to run the pipeline and clicking resources, it scanned master branch by default. When fixing the indentation error on the master branch (which above error was referring to, it just didn't say which branch) the problem was solved.

I have installed the official Owasp plugin. I was using an offshoot with sonarqube integration. Besides this I've built the project on the same agent just before running the check. This ensures that the files to be scanned are available on the agent (was having difficulties with artifactPublish and artifactDeploy tasks).

With pathlib, you should be doing something like the following.

This uses the .parts attribute to do the splitting of path.parent into components reliably. You shouldn't assume the directory separator.

Then, reconstruct the rest of the path by passing it back to pathlib.Path.

To the best of my knowledge (which is several years of using pip-tools), pip-tools will always give you a stable tree so long as you do then install dependencies only from the "locked" requirements file.

I solved it and I would like to share my solution for it;

I followed the steps here: https://github.com/aws/aws-greengrass-core-sdk-js

To download the NodeJS:

Based on the comments.

There is no native package for python 3.7 on Amazon Linux 1. Thus, it should be compiled as shown here. The compilation steps include:

1. Installation of dependencies,

This is because your report is written to Common.TestResultsDirectory which is c:\agent_work\1\TestResults (for Microsoft Hosted agents), and publish test task looks in System.DefaultWorkingDirectory which is c:\agent_work\1\s.

Please try:

@Ashwani, we are seeing the same. The NIST NVD feeds (both 1.0 and 1.1) were having issues last week. The 1.1 feed (https://nvd.nist.gov/feeds/json/cve/1.1/nvdcve-1.1-modified.meta) looks as if it is working correctly again today. However, the 1.0 feed still looks like it is offline or broken. We've been unable thus far to try and make anyone at NIST aware of any potential issue with the feed.