New Features:
- JHFB-144 - Tag Checker
Bugfixes:
- JHFB-137 - Broken validation of the exception group settings
Bug-fix:
Further information you will find in our release notes
Bug-fix:
Further information you will find in our release notes
New Features:
Bugfixes:
Preparation Frozen Branch Support:
Preparation for Frozen Branch Support, which can be ordered additionally in the later part of this year. You are welcome to ask about prices and offers already now
New Features:
Bugfixes:
Preparation Frozen Branch Support:
Preparation for Frozen Branch Support, which can be ordered additionally in the later part of this year. You are welcome to ask about prices and offers already now
Correct some internals and remove some typos. The behaviour has not been changed
see release notes for further information
Correct some internals and remove some typos. The behaviour has not been changed
see release notes for further information
New features:
Bugfixes:
see release notes for further information
New features:
Bugfixes:
see release notes for further information
New features:
see release notes for further information
New features:
see release notes for further information
New features:
see release notes for further information
New features:
see release notes for further information
JHFB-113 - Configured project application links not respected
see release notes for further information
JHFB-113 - Configured project application links not respected
see release notes for further information
JHFB-112 - "Skip commits based on keyword" configuration has no affect to local commit checks
JHFB-112 - "Skip commits based on keyword" configuration has no affect to local commit checks
JHFB-110 Support local Git Hook - Check commit message at commit time
Now it is possible to check a commit messages not only at push time. Since this version the commit message can be evaluated also at commit time. We have introduced a new Rest-API endpoint, which enables you to check a commit message at any time in your process. For example in a Git hook, which is probably the major task of this API.
Check our How-To: How to configure a local commit hook?
In this How-To we have provided a commit-msg hook based on Python3, which will use this Rest-API to evaluate a commit message during runtime.
JHFB-110 Support local Git Hook - Check commit message at commit time
Now it is possible to check a commit messages not only at push time. Since this version the commit message can be evaluated also at commit time. We have introduced a new Rest-API endpoint, which enables you to check a commit message at any time in your process. For example in a Git hook, which is probably the major task of this API.
Check our How-To: How to configure a local commit hook?
In this How-To we have provided a commit-msg hook based on Python3, which will use this Rest-API to evaluate a commit message during runtime.
The minor release will provide the following new features:
If you would like to see further details, please check out user guide:
https://devopssystems.atlassian.net/wiki
If you have any further questions, please contact our help desk
https://devopssystems.atlassian.net/servicedesk/customer/portal
The minor release will provide the following new features:
If you would like to see further details, please check out user guide:
https://devopssystems.atlassian.net/wiki
If you have any further questions, please contact our help desk
https://devopssystems.atlassian.net/servicedesk/customer/portal
Bugfixes:
Bugfixes:
Bugfixes:
JHFB-94 - Compatibility Bitbucket 6.x
JHFB-94 - Compatibility Bitbucket 6.x
Bugfixes:
Bugfixes:
Bugfix:
JHFB-85 - IllegalStateException regarding custom fields
Bugfix:
JHFB-85 - IllegalStateException regarding custom fields
JHFB-82 - The branch creation from Jira or via Web is broken
JHFB-82 - The branch creation from Jira or via Web is broken
Bugfixes
Bugfixes
New Features:
Bugfixes:
New Features:
Bugfixes:
Due to a refactoring from the major release 3.x to the major release 4.x, the merge hook got a new hook key. This is the reason, why Bitbucket can not find the already configured 3.x settings in the 4.x merge hook. But the hook settings are still available.The automated migration of the merge settings has been disabled. Alternatively we offer a migration guide wich enables you to migrate the settings from 3.x to 4.x
The migration guide you can find in our FAQ: https://devopssystems.atlassian.net/wiki/x/ZAAE
Attention:
If the merge hook has valid settings, the merge hook will be enabled automatically after the migration. If there are valid settings but you do not plan to use the merge hook, you need to disable the merge hook after the update.
Bugfix:
Bugfixes:
Bugfix:
Bugfixes:
Bugfix:
New features:
Bugfixes:
Bugfix:
New Feature:
Bugfix:
JHFB-26 - Confusing licensing error message
Bugfix:
Bugfix:
New Features