You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 12, 2019. It is now read-only.
I started using this library for a project that interacts with TeamCity Professional 10.0.2 (build 42234) installed in the same network, but on a different machine.
Although the fields startDate, queuedDate and finishedDate are populated on the server and in the subsequent XML or JSON received using the API, they aren't available in the corresponding Build entity in the list retrieved using tcClient.Builds.AllBuildsOfStatusSinceDate(DateTime.MinValue, BuildStatus.SUCCESS). Furthermore, the Agent, BuildConfig, Changes and several other properties are either null or with default type's values.
Is that by design or it wasn't yet implemented? Thank you.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I started using this library for a project that interacts with TeamCity Professional 10.0.2 (build 42234) installed in the same network, but on a different machine.
Although the fields startDate, queuedDate and finishedDate are populated on the server and in the subsequent XML or JSON received using the API, they aren't available in the corresponding Build entity in the list retrieved using tcClient.Builds.AllBuildsOfStatusSinceDate(DateTime.MinValue, BuildStatus.SUCCESS). Furthermore, the Agent, BuildConfig, Changes and several other properties are either null or with default type's values.
Is that by design or it wasn't yet implemented? Thank you.
The text was updated successfully, but these errors were encountered: