Now, you can see the detailed test statistics without switching to the classic mode. The highly demanded Test History page gets a fresh look in this EAP. One by one, we reproduce all classic TeamCity pages in our experimental UI.
Experimental UI updates New Test History page Opposite the required service, click the edit button and enter an external username.Ĭlick Save changes. For this, open a user profile in TeamCity and scroll down to the Authentication Settings section. TeamCity administrators can also map external user accounts with all existing TeamCity users. Since this EAP, you can connect your external accounts in User Profile | Authentication Settings so TeamCity is able to recognize you if you sign in with any of them.
#TEAMCITY DEARBORN HOW TO#
Read how to enable the OAuth support in our previous EAP notes. TeamCity administrators can restrict authentication to users from specific GitLab groups. Otherwise, TeamCity will create a new user profile. If a user with the provided email is already registered in TeamCity, you will be authenticated as this user. In EAP3, the users can also sign into TeamCity with their accounts.Ĭlick the respective icon when signing in, and you will be redirected to a regular authentication form in GitLab. We had already added the support for and Bitbucket Cloud in previous EAP builds. Since TeamCity 2020.2, users will be able to authenticate in TeamCity with their external accounts using OAuth. OAuth authentication: support and mapping accounts with existing TeamCity users Read how to configure the new runner in our EAP documentation. If you were using the old plugin to run your Python projects, we highly recommend switching the respective build steps to the bundled runner.Īs the new runner offers extra settings, the existing steps cannot be converted automatically and have to be reconfigured manually.
#TEAMCITY DEARBORN PLUS#
For example, if you have 10 agent licenses, you can simultaneously run 10 agents plus 10 agentless builds. You can run as many agentless build steps in parallel as there are agent licenses on your server. Since this version, if there are no more steps that depend on the agent, the build statuses can be reported directly to the TeamCity server using REST API. In the previous versions of TeamCity, an agent would wait until the external tool is done with its tasks which might take a long time. This approach allows saving cloud agent work time and is optimal for configurations that use third-party tools for finalizing a build: for example, to run numerous tests or deploy a project. This agent becomes available to other builds, and the current build completes its steps in the “agentless” mode. Now, your build can send an instruction to “release” the agent. Normally, a running build occupies a build agent until the very finish, even if its final steps are executed outside TeamCity. TeamCity introduces agentless build steps – steps that can run without a build agent, in an external software. In these release notes, we describe the most exciting updates.
TeamCity 2020.2 EAP3 comes with 90 improvements and fixes. Today we are releasing our third Early Access Program build for TeamCity 2020.2! OAuth authentication: support and mapping accounts with existing TeamCity users.
0 kommentar(er)
