Release Notes v4.0
We’re thrilled to announce that we’ve released Code Review Assisant 4.0 on 🎉
Download on the Atlassian Marketplace for Bitbucket Server
Removal of code cross-referencing feature based on ctags for Bitbucket >= 7.0
Due to Bitbucket API changes in version 7, we cannot provide the ctags feature anymore. This is why code cross-referencing is not added to pull requests anymore in newer Bitbucket versions.
Bitbucket 7 compatibility
Some internal changes to allow compatibility with Bitbucket 7.
Support multi-line static code analysis output
Some static code analyzers like pydocstyle emit multi-line output for found code violations. To support that, we now consider multiple lines when applying the configured regular expressions to scan the analyzer output.
Ignore LFS files when cloning a repository
When cloning a repository to execute static code analyzers, we now ignore Git LFS files to reduce the used disk space, but also because these are often binaries that should not get analyzed anyway.
Annotations with built-in CodeNarc are not shown due to relative-paths in issue output
Upgrade to CodeNarc 1.4
Increased timeout for running external analyzers
Resolved issues in 4.0.1 on
Issues for new commits are not always added deterministically to the pull request
Upgraded built-in CodeNarc to version 1.6.1
Merge checks are not applied for custom static analyzers in Bitbucket >= 7.2
Got rid of enforcing %f and %fs for files because it does not work with some analyzers like PMD when single command invocation with all files is required
Settings like regexes from locally defined custom analyzers are not applied