-
Notifications
You must be signed in to change notification settings - Fork 123
Open
Description
We are using the version from July 31 in TC 2018.1.1. We specified particular credentials in the "Add Build Tags" build step. It works 99% of the time, but on rare occasions in random builds we get this:
[15:02:23]prepare-internal-credentials:
[15:02:23]
[15:02:23]prepare-custom-credentials:
[15:02:23] [echo] using custom credentials
[15:02:23]
[15:02:23]prepare-tags:
[15:02:23]
[15:02:23]addTags:
[15:02:23] [http] HTTP Request
[15:02:23] [http] ********************
[15:02:23] [http] URL: https://buildserver/httpAuth/app/rest/8.0/builds/id:1302210/tags
[15:02:23] [http] Method: POST
[15:02:23] [http] Content-Type: application/xml
[15:02:23] [http] Entity: yes
[15:02:23] [http] ------ BEGIN ENTITY ------
[15:02:23] [http] <tags><tag>ObfuscatedTag1</tag><tag>ObfuscatedTag2</tag></tags>
[15:02:23] [http] ------- END ENTITY -------
[15:02:23] [http]
[15:02:23] [http] HTTP Response
[15:02:23] [http] ********************
[15:02:23] [http] Status: 401
[15:02:23]
[15:02:23]BUILD FAILED
[15:02:23]E:\Obfuscated\Obfuscated\build9079597898286185054.tmp:73: Expected Status [204] but got [401] for URI [https://buildserver/httpAuth/app/rest/8.0/builds/id:1302210/tags]
I can't figure out the cause. Credentials in the build steps do not change between builds. Is using "8.0" in the URL a problem? Should it use the most recent endpoint?
Is it possible that TeamCity cannot handle these REST calls if multiple calls happen at the same time?
Metadata
Metadata
Assignees
Labels
No labels