This repository has been archived by the owner on May 1, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
Home
Ari Kamen edited this page Apr 22, 2016
·
20 revisions
Official Black Duck documentation:
1.4.0 - https://github.com/blackducksoftware/integration-all/blob/master/Hub_TeamCity_1.4.0.pdf
Failure conditions based on the policy API support are now available:
- You can configure the failure condition based on policy through the UI.
- The build fails if there are any counts regarding policy violations.
- The build logs the policy counts.
- A version of the Hub that does not support the policy API logs that it is not compatible for the policy API.
- The build passes even if the policy failure condition is not configured.
- Addressed an issue wherein project scan failure conditions now wait for the Bill of Materials to be
- updated.
- Addressed an issue wherein duplicate scan targets were not validated.
- Addressed an issue wherein TeamCity builds were failing if the target already existed.
- If an authenticated proxy server has been configured, then all communications from the plugin to Black Duck Hub are now done through the authenticated proxy server.