NET framework were installed on the agent. TeamCity agents before version 10 used to report DotNetFramework4.0_* properties whenever any of 4.x versions of. The details are also logged into teamcity-auth.log.Ĭhanges in agent properties reporting.
The non-browser clients which reuse authentication by supplying the TCSESSIONID cookie with the request, need to be updated to supply the "Origin" HTTP header with the value the same as the host the request is being sent to.If the check fails, you get the HTTP 403 response with the details of the failed check. If you use non-bundled clients which perform HTTP GET requests to TeamCity, some of the GET requests (those which change the state of the server, like stop working in 2017.1, please change the requests to use POST instead of GET While this has been the recommended setup for a long time, now it becomes critical for the TeamCity web UI functioning Also, it should not modify the "Origin" and "Referer" headers present in the original request. If you use a reverse proxy before TeamCity, the proxy should not change the original "Host" request header (this typically requires configuring the proxy to set the Host header to the original request value). TeamCity now implements CSRF protection to improve web UI security and this introduces several changes in behavior which might affect your installation. nupkg files are now indexed on the agent side instead of the server which could slightly increase the time of builds for projects with the NuGet Feed feature and the automatic package indexing enabled or for builds with NuGet Packages Indexer build feature.ĬSRF Protection: Modifying GET requests and Proper Proxy configurations It is recommended to switch to new URL in your projects. The enabled default NuGet feed with all published packages accessed by URL /app/nuget/v1/FeedService.svc/ is now moved to the Root project feed /app/nuget/feed/_Root/default/v2/.
You now need to explicitly specify the URL from the NuGet Feed page in the Project Settings. The following NuGet feed-related build parameters are deprecated: The "NuGet packages indexer" build feature can be added to build configurations whose artifacts should be indexed. tools/maven3.4.5/bin/mvn should be replaced with %3.4.5%/bin/mvn.Ĭonfiguration of the NuGet feed was moved from the server level to the project level: now each project can have its own feed.
Paths like /tools/ used in TeamCity settings should be changed to the %teamcity.tool.% parameter reference. If some of your builds use tools on agent assuming their locations under the /tools directory, such references should be changed to a TeamCity-provided parameter reference. If some tool is referenced via this parameter, TeamCity will make sure this tool is present on the agent before the build logic starts executing. configuration parameters to collect the set of tools used by the build.
#RUBYMINE 6.0.3 LICENSE KEY UPDATE#
You might need to update the build configuration settings so TeamCity knows which tools are required by the builds.īefore starting a build on an agent, TeamCity checks for the references to teamcity.tool. Agent tools (located under the /tools directory on agents) are now transferred to an agent not on the agent upgrade, but right before the first build that uses the respective tool.
0 kommentar(er)
