Git Plugin

1.2.1

Enhancement: Bitbucket Cloud Access Tokens

Previous released supported authenticating with Bitbucket cloud only via app passwords. By default, the maven plugin now expects an access token to be supplied in the bitbucket.token field.

App passwords are still supported, but discouraged. To use an app password the parameter bitbucket.useAppPassword must bet set to true.

A configuration change must therefore be made when upgrading

When an access token is used to authenticate, the bitbucket.user parameter no longer needs to be set. This parameter is required only when using app passwords.

1.2.0

Relocate Maven Co-ordinates

This release moves the plugins to com.arcmutate. Previous releases were published as com.groupcdg.

1.1.4

Enhancement: Support Deletion of Resolved Comments

Arcmutate now supports deleting Bitbucket server comments that have been marked as resolved by a user. Previously these read-only comments were left in place.

1.1.3

Bug Fix: Do No Error for Resolved Comments

Recent versions of Bitbucket server allow comment threads to be marked as resolved and placed in a read only state. If a user resolved a comment created by Arcmutate, the plugin threw an error when attempting to delete or update the resolved comment.

1.1.2

Enhancement: Optionally Create Tasks on Bitbucket Server

When the gitci level is set to error, mutations will now be created as tasks on bitbucket server.

Enhancement: Retain Outdated Mutant Descriptions

For Bitbucket server, when a mutation comment cannot be deleted due to replies, the original text will now be retained when marking the comment as outdated.

1.1.1

Enhancement: Report Number of Covering Tests

Previously the pull request integrations reported the number of tests run against each mutant. This did not work well when a history file was also used, as the number of executed tests would be zero after the first analysis if the code and tests around a mutant were not changed.

The number of covering tests for each mutant is now reported instead. This is a stable figure, even when a history file is in use, and arguably more useful information to be presented with when assessing a surviving mutant.

1.1.0

Remove Lambda Description Modifications

Previous versions of the plugin updated the names of mutated lambdas to be more human readable. This functionality is now provided by the arcmutate base plugin. If it is not already configured for your project it should be installed when upgrading to 1.1.0.

1.0.12

Enhancement: Expand Licence Search

1.0.11

Bug Fix: Broken Table For Bitbucket Server

When all mutations were killed, the table failed to render correctly on bitbucket server which requires additional whitespace in the markdown.

1.0.10

Bug Fix: Do Not Fail When No Mutations in Mixed Mode

The pitest failWhenNoMutations flag is now autoset to false when running in git mixed mode. This makes the behaviour the same across all three modes.

1.0.9

Enhancement: Detect Unchanged Modules in Test and Mixed Mode

When a module contains no git changes, arcmutate will now stop processing without running tests when operating in git-test or git-mixed modes. This brings the behaviour in line with normal git mode, and potentially saves significant processing time.

1.0.8

Bug Fix: Handle Comments With Replies

Comments with replies cannot be deleted on BitBucket Server, which could cause the plugin to fail when updating an MR (BitBucket cloud is unaffected).

The plugin will now replace the contents of comment that cannot be deleted with a fixed message.

1.0.7

Enhancement: Delete Summaries In GitHub

Adds the option to delete past summary comments in GitHub PRs. This is controlled by a new deleteOldSummaries parameter which defaults to false.

1.0.6

Enhancement: Mixed Mode

Introduces a new mode GIT_MIXED combining the behaviour of the test and change based modes. Code will be considered for mutation if it has been modified, or if it is part of a class where one or more lines are exercised by a modified test.

Enhancement: Auto Add Test Source Roots

GIT_TEST and GIT_MIXED mode require the source roots of the test code to be passed to pitest as well as the production source roots. As these will often not be configured, the plugin will attempt to auto-add test directories. If a directory is configured of the form src/main/x the plugin will add src/test/x if it exists.

1.0.5

Enhancement: Prevent duplicates in annotations.json

1.0.4

Bug Fix: Handle Concurrent Changes to Git History

On some platforms, a fatal error would occur if an external process modified a version controlled file. Most often this occurred when lock files, or other files that were not intended to be version controlled, were accidentally included due to missing entries in the .gitignore.

These scenarios are no longer treated as an error, although the inclusion of non source files in the git history may result in additional processing and slow performance.

1.0.3

Enhancement: Improved Logging

Small enhancement to logging to ensure the last accessed file is recorded when an IOException occurs.

1.0.2

Bug Fix: Ensure Resources Released

Fix for potential resource leak when analysing very large changesets.

1.0.1

Enhancement: Dynamic Licence Retrieval

See Licence Management for details.

1.0.0

New Feature: Test Driven Change

Additional mode of operating, see test based mode

Enhancement: Automaticaly Unset FailWhenNoMutations

When the plugin is activated pitest’s failWhenNoMutations property is now automatically unset. This removes the need for additional config when the changes in the git history do not include mutable code.