Is it possible to tag TeamCity builds using service messages (or some other programatic way)?

teamcity service messages example
teamcity rest api
teamcity build queue api
teamcity-messages
teamcity automatically tag build
teamcity build step custom script
teamcity test results reporting
teamcity custom script

Is it possible to tag TeamCity builds using service messages or some other programmatic way from a build step maybe...?

How can this be done?

See also the following stackoverflow discussion:

Programatically pin a build in Teamcity

Moreover, since there were two open questions on stackoverflow and I had the same problem, I wrote a TeamCity plugin that solves it:

https://github.com/echocat/teamcity-buildTagsViaBuildLog-plugin

Is it possible to tag TeamCity builds using service messages, Is it possible to tag TeamCity builds using service messages (or some other builds using service messages (or some other programatic way)? - teamcity-8.0 See also the following stackoverflow discussion: Programatically pin a build in YAML is pretty new, and there is not, as far as I know, an easy way to convert it to� Using the Pin/Unpin build dialog, where you can tag the build in addition to pinning it. For builds with snapshot dependencies, there is an option to pin and tag the build as well as its snapshot dependencies.

There is a VCS labelling in TeamCity, you can tag when a build successful, or on each build. Does it correspond to what you're looking for?

Build Script Interaction with TeamCity - Help, service messages (or some other programatic way)? -. is possible tag teamcity builds using service messages or other programmatic way build step maybe. Yes, currently there is no automatic method for tagging or pinning within the workflow, so you need to have a build step that will do it using the API, typically a command line script. 0

Yes, there is. You can use the REST API, as described here. Basically,

Adding a tag using plain text
curl -s  --header "Authorization: Bearer $TOKEN" \
    -H 'Content-Type: text/plain' \
    "https://ci.ACME.com/app/rest/builds/5375/tags --data tag-1 
tag-1
Reading the list of tags as json
curl -s -H 'Accept: application/json'  \
     -H "Authorization: Bearer $TOKEN" \
     "https://ci.ACME.com/app/rest/builds/5375/tags"
{"count":1,"tag":[{"name":"tag-1"}]}
Overwriting tags using json, getting it back as xml (the default)
curl -s  --header "Authorization: Bearer $TOKEN" \
     -H 'Content-Type: application/json' -X PUT \
    "https://ci.ACME.com/app/rest/builds/5375/tags \
     --data '{"count":2,"tag":[{"name":"tag-A"},{"name":"tag-B"}]}'
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><tags count="2"><tag name="tag-A"/><tag name="tag-B"/></tags>

Build Tag - Help, If TeamCity doesn't support your testing framework or build runner out of the box, you can It is recommended to output a single service message per line (that is divide You can report messages for a build log in the following way: All the other test messages (except for testIgnored ) with the same name� Hi Matthew, Such feature is not implemented in TeamCity now. Please watch and vote for the related feature request. As of now you can use Add build tags meta-runner which uses REST API.

DevOps, Additionally, you can search for builds with particular tags using the search field. To tag a build: The TeamCity web UI provides the following ways� Service Messages. Service messages are used to pass commands/build information to a TeamCity server from the build script. In order to be processed by TeamCity, they should be printed into a standard output stream of the build (otherwise, if the output is not in the service message syntax, it should appear in the build log).

Get started guide for developers on Azure, You could decide to exclusively use the cloud-based services provided by AWS, Chef, Codenvy, HashiCorp Terraform, Octopus Deploy, and JetBrains TeamCity. According to G2 Crowd, the main competitors to AWS CodeBuild, in the Build using the main.yml file and referencing the create or delete Ansible Tags. By using a dedicated service message in your build script, you can dynamically update build parameters of the build right from a build step. The changed build parameters will be available in the build steps following the modifying one.

Dynamically setting TeamCity version numbers based on the current , It provides guidance and direction that you need to start building new With all the services that Azure offers, it can be an intimidating task to your entire infrastructure as a virtual machine (VM)? Can you use the These tools include GitHub webhooks, Jenkins, Azure DevOps, TeamCity, and others. go to the Comments and Tags tab and add/modify the build tag By clicking a tag, you filter out all of the builds in the history: only the builds marked with the tag are displayed. Additionally you can search for builds with particular tags using the search field .

Comments
  • VCS labeling is configured on the Build Features page of the Build Configuration settings. You can add a build features, and you choose how you want to label your sources. This works with TeamCity 8.1. Priro to that version, it's in VCS Settings of the Build Confiuration Settings
  • You are basically describing labelling on the VCS level, not the level of the build server. TeamCity has tagging features of its own, which is slightly confusing when talking of tags in VCS at the same time.