matmalkowski / netcore-teamcity-api Goto Github PK

In TeamCity.cs the TeamCityConnectionSettingsBuilder's method UsingSSL() should be given the argument usingSSL. Currently there is no way to specify the builder to use standard http and not https. I believe line 10 should be the following

var connectionConfig = new TeamCityConnectionSettingsBuilder().ToHost(host).UsingSSL(usingSSL).AsUser(userName, password).Build();

Project features (e.g. issue trackers, versioned settings, custom charts, shared resources and third-party report tabs) are exposed as entries under the "project" node and via dedicated requests.

• List of project features: http://teamcity:8111/app/rest /projects//projectFeatures
• List features with filtering: http://teamcity:8111/app/rest/projects//projectFeatures?locator= e.g. to find all issue tracker features of GitHub type, use locator "type:IssueTracker,property(name:type,value:GithubIssues)"
• Edit features: GET/DELETE/PUT http://teamcity:8111/app/rest /projects//projectFeatures/

It should be public as QueuedBuildService propose public Run method.

• Get project details: GET http://teamcity:8111/app/rest/projects/
• Delete a project: DELETE http://teamcity:8111/app/rest/projects/
• Create a new empty project: POST plain text (name) to http://teamcity:8111/app/rest/projects/
• Create (or copy) a project: POST XML to http://teamcity:8111/app/rest/projects . Also see an example.
• Edit project parameters: GET/DELETE/PUT http://teamcity:8111/app/rest/projects//parameters/<parameter_name> (produces XML, JSON and plain text depending on the "Accept" header, accepts plain text and XML and JSON) Also supported are requests .../parameters/<parameter_name>/name and .../parameters/<parameter_name>/value.
• Project name/description/archived status: GET/PUT http://teamcity:8111/app/rest/projects//<field_name> (accepts/produces text/plain) where <field_name> is one of "name", "description", "archived".
• Project's parent project: GET/PUT XML http://teamcity:8111/app/rest/projects//parentProject

• GET http://teamcity:8111/app/rest/buildQueue
  Supported locators:
  project:
  buildType:
• Get details of a queued build:
  GET http://teamcity:8111/app/rest/buildQueue/id:XXX
  For queued builds with snapshot dependencies, the revisions are available in the revisions element of the queued build node if a revision is fixed (for regular builds without snapshot dependencies it is not).
• Get compatible agents for queued builds (useful for builds having "No agents" to run on)
  GET http://teamcity:8111/app/rest/buildQueue/id:XXX/compatibleAgents
  Examples:
• List queued builds per project:
  GET http://teamcity:8111/app/rest/buildQueue?locator=project:
• List queued builds per build configuration:
  GET http://teamcity:8111/app/rest/buildQueue?locator=buildType:

• List all VCS roots: GET http://teamcity:8111/app/rest/vcs-roots add locator= parameter to list only the VCS roots matched
• Get details of a VCS root/delete a VCS root: GET/DELETE http://teamcity:8111/app/rest/vcs-roots/ , where "" can be "id:" or other VCS root locator
• Create a new VCS root: POST VCS root XML (the one like retrieved for a GET request for VCS root details) to http://teamcity:8111/app/rest/vcs-roots
  Also supported:
• GET/PUT http://teamcity:8111/app/rest/vcs-roots/ /properties/<property_name>
• GET/PUT http://teamcity:8111/app/rest/vcs-roots//<field_name>, where <field_name> is one of the following: name, shared, project (post project locator to "project" to associate a VCS root with a specific project).
• List VCS root instances: GET http://teamcity:8111/app/rest/vcs-root-instances?locator=
  A "VCS root" is the setting configured in the TeamCity UI, "VCS root instance" is the internal TeamCity entity which is derived from the "VCS root" to perform actual VCS operation.
  If the VCS root has no %-references to parameters, a single VCS root corresponds to a single "VCS root instance".
  If a VCS root has %-reference to a parameter and the reference resolves to a different value when the VCS root is attached to different configurations or when custom builds are run, a single "VCS root" can generate several "VCS root instances".

Since TeamCity 10.0 :

There are two endpoints dedicated at using in commit hooks from the version control repositories:

• POST http://teamcity:8111/app/rest/vcs-root-instances/checkingForChangesQueue?locator= - schedules checking for changes for the matched VCS root instances and returns the list of VCS root instances matched (just like GET http://teamcity:8111/app/rest/vcs-root-instances?locator= )
• POST http://teamcity:8111/app/rest/vcs-root-instances/commitHookNotification?locator= - schedules checking for changes for the matched VCS root instances and returns plain-text human-readable message on the action performed, HTTP response 202 in case of successful operation
  Both perform the same action (put the VCS root instances matched by the ) to the queue for "checking for changes" process and differ only in responses they produce.
  Note that since the matched VCS root instances are the same as for .../app/rest/vcs-root-instances?locator= request and that means that by default only the first 100 are matched and the rest are ignored. If this limit is hit consider tweaking the to match less instances (recommended) or increase the limit e.g. by adding ",count:1000" to the locator.

• List tests:
  GET http:// teamcity :8111/app/rest/testOccurrences?locator=:
  Supported locators:
  build
  build:(id:buildId),muted:true (tests which were muted when the build ran)
  build:(id:buildId),currentlyMuted:true (failures were not muted, but the tests were muted since the failure)
  test
  currentlyFailing:true,affectedProject:
  currentlyMuted:true,affectedProject:
  Examples:
  List all build's tests: GET http://teamcity:8111/app/rest/testOccurrences?locator=build:
  Get individual test history:
  GET http:// teamcity :8111/app/rest/testOccurrences?locator=test:
  List build's tests which were muted when the build ran:
  GET http://teamcity:8111/app/rest/testOccurrences?locator=build:(id:XXX),muted:true
  List currently muted tests (muted since the failure):
  GET http://teamcity:8111/app/rest/testOccurrences?locator=build:(id:XXX),currentlyMuted:true
  Supported test locators:
  "id:" available as a part of the URL on the test history page
  "name:"

Since TeamCity 10 there is experimental support for exposing single test invocations / runs:

• Get invocations of a test:
  GET http:// teamcity :8111/app/rest/testOccurrences? locator=build:(id:XXX),test:(id:XXX)&fields=$long,testOccurrence($short,invocations($long))

List all test runs with all the invocations flattened:

• GET http:// teamcity :8111/app/rest/testOccurrences? locator=build:(id:XXX),test:(id:XXX) ,expandInvocations:true

• Build Configuration/Template details: GET http://teamcity:8111/app/rest/buildTypes/ (details on the Build Configuration locator).
  Please note that there is no transaction, etc. support for settings editing in TeamCity, so all the settings modified via REST API are taken into account at once. This can result in half-configured builds triggered, etc. Please make sure you pause a build configuration before changing its settings if this aspect is important for your case.
  To get aggregated status for several build configurations, s ee Build Status Icon section.

• Get/set paused build configuration state: GET/PUT http://teamcity:8111/app/rest/buildTypes/ /paused (put "true" or "false" text as text/plain)

• Build configuration settings: GET/DELETE/PUT http://teamcity:8111/app/rest/buildTypes/ /settings/<setting_name>

• Build configuration parameters: GET/DELETE/PUT
  http://teamcity:8111/app/rest/buildTypes/ /parameters/<parameter_name> (produces XML, JSON and plain text depending on the "Accept" header, accepts plain text and XML and JSON). The requests .../parameters/<parameter_name>/name and .../parameters/<parameter_name>/value are also supported.

• Build configuration steps: GET/DELETE http://teamcity:8111/app/rest/buildTypes/ /steps/<step_id>

• Create build configuration step: POST http://teamcity:8111/app/rest/buildTypes//steps. The XML/JSON posted is the same as retrieved by GET request to .../steps/<step_id> except for the secure settings like password: these are not included into responses and should be supplied before POSTing back
  Features, triggers, agent requirements, artifact and snapshot dependencies follow the same pattern as steps with URLs like:
  http://teamcity:8111/app/rest/buildTypes//features/
  http://teamcity:8111/app/rest/buildTypes//triggers/
  http://teamcity:8111/app/rest/buildTypes//agent-requirements/
  http://teamcity:8111/app/rest/buildTypes//artifact-dependencies/
  http://teamcity:8111/app/rest/buildTypes//snapshot-dependencies/
  Since TeamCity 10, it is possible to disable/enable artifact dependencies and agent requirements:

• Disable/enable an artifact dependency PUT http://teamcity:8111/app/rest/buildTypes//artifact-dependencies//disabled (put " true " or "false" text as text/plain)

• Disable/enable an agent requirement PUT http://teamcity:8111/app/rest/buildTypes//agent-requirements//disabled (put " true " or "false" text as text/plain)

• Build configuration VCS roots: GET/DELETE http://teamcity:8111/app/rest/buildTypes//vcs-root-entries/

• Attach VCS root to a build configuration: POST http://teamcity:8111/app/rest/buildTypes//vcs-root-entries . The XML/JSON posted is the same as retrieved by GET request to http://teamcity:8111/app/rest/buildTypes//vcs-root-entries/ except for the secure settings like password: these are not included into responses and should be supplied before POSTing back.

• Create a new build configuration with all settings: POST http://teamcity:8111/app/rest/buildTypes . The XML/JSON posted is the same as retrieved by GET request. (Note that /app/rest/project/XXX/buildTypes still uses the previous version notation and accepts another entity.)

• Create a new empty build configuration: POST plain text (name) to http://teamcity:8111/app/rest/projects//buildTypes

• Copy a build configuration: POST XML to http://teamcity:8111/app/rest/projects//buildTypes

• Read, detach and attach a build configuration from/to a template: GET/DELETE/PUT http://teamcity:8111/app/rest/buildTypes//template (PUT accepts template locator with "text/plain" Content-Type)