Cake.Issues.Sarif 4.8.0

Support for reading SARIF compatible files using the Cake.Issues addin for Cake Build Automation System

NOTE: This is the version of the addin compatible with Cake .NET Tool. For addin compatible with Cake Frosting see Cake.Frosting.Issues.Sarif.

The SARIF support for the Cake.Issues addin for Cake allows you to read SARIF compatible files.

Cake.Issues redefines issue management within the Cake build system by offering a comprehensive, universal, and extensible solution. The unique capabilities of the addins empower development teams to enforce coding standards, generate insightful reports, seamlessly incorporate various linting tools, and streamlining the integration with pull requests. With its modular architecture and extensive set of aliases, Cake.Issues provides a future-proof infrastructure for issue management in Cake builds, fostering a more efficient and adaptable development process.

For more information and extensive documentation see the Cake.Issues website. For general information about the Cake build automation system see the Cake website.

How to use

Integrating Cake.Issues into your Cake build is straightforward. With minimal setup, teams can enjoy the benefits of enhanced code quality management seamlessly integrated into their existing build pipeline.

After adding the addin the SARIF log file can be parsed:

Task("Analyze").Does(() =>
{
    var logPath = @"c:\build\log.sarif";
    var repoRootPath = @"c:\repo";

    // Read issues.
    var issues =
        ReadIssues(
            SarifIssuesFromFilePath(logPath),
            repoRootPath);

    Information("{0} issues are found.", issues.Count());
});

Support & Discussion

For questions and to discuss ideas & feature requests, use the GitHub discussions on the Cake GitHub repository, under the Extension Q&A category.

Contributing

Contributions are welcome. See Contribution Guidelines.

License

MIT License - Copyright © Cake Issues contributors

Binary distributions for some addins contain third-party code which is licensed under its own respective license. See LICENSE for details.