...
| Setting | Description |
|---|---|
| Enable users synchronization | Allows importing users and their details from Hub to TeamCity. |
| Update user profiles in TeamCity | The user name, email and VCS usernames in TeamCity will be updated with data from the user profile in Hub on the first synchronization. If any of this data will be later modified in TeamCity, the changed data will not be imported from Hub on the next synchronization. |
| Create user accounts in TeamCity | New users (those existing in Hub but not existing in TeamCity) matched by the users filter will be imported to TeamCity with their login details, emails and VCS usernames. All the imported users will have a Hub ID in TeamCity. If a user with the same name exists in TeamCity and Hub, the user is not synchronized until they login to TeamCity via Hub. The existing TeamCity users with no match in Hub will remain intact.
|
| Delete user accounts from TeamCity | If a user account is deleted in Hub (banned/ merged) or is not matched by the filter anymore, it will also be deleted in TeamCity as well.
|
Clicking SynchronizeSynchronize now launches synchronization manually. After the synchronization is finished, the results will be reported on the page.
Jb hidden data start
Enabling access to TeamCity from Hub Dashboard
After registering of TeamCity service in Hub, TeamCity widgets can be configured on Hub dashboard. But widgets will not work until additional configuration is performed on TeamCity side.
Hub Dashboard uses TeamCity REST API to access TeamCity data. But since REST API requests are performed on behalf of the current user and from different host, REST API CORS settings should be configured appropriately.
For this two internal properties should be set:
- rest.cors.origins=<hub url>
- rest.cors.optionsRequest.allowUnauthorized=true
| Jb hidden data end |
|---|
Plugin Development Status
...