TeamCity Kanpur 2019.1 EAP3 is here

We are glad to present you the third and final Early Access Preview (EAP) version of TeamCity 2019.1.

In this EAP, we are introducing the following features:

  • Improvements for Amazon spot instances
  • Build artifacts publishing options
  • Docker requirement for build agents
  • Parsing of Go tests
  • Token-based authentication
  • New documentation website

Improvements for Amazon spot instances

Many of our users benefit from launching cloud images on Amazon spot instances. The spot fleet functionality allows you to use instances even more efficiently.

With a spot fleet option enabled for an image, you can apply the capacity allocation strategy which suits your project the best.

spot-fleet-option

Build artifacts publishing options

Build artifacts publishing is now more flexible. Previously, the artifacts were published only for completed builds, either successful or failed. We have added two new options:

  • Publish artifacts only if a build is completed successfully. This allows saving disk space by restricting publishing only to cases when all build steps are successful.
  • Publish artifacts for all builds, even for interrupted ones. This helps investigate an interruption problem by inspecting the artifacts.

Docker requirement for build agents

The bundled Docker Support plugin now sets requirements for build agents. If you add the ‘Docker Support’ feature to a build configuration, TeamCity will check all available agents and put those with installed Docker to the ‘Compatible agents’ list.

docker-requirement

Parsing of Go tests

TeamCity now can parse Go tests. To enable the Go processor for a project, add the ‘Golang’ feature to a build configuration. To generate tests:

  • either append the ‘-json’ flag to the ‘go test’ command in the script of a Command Line build runner
  • or add the ‘env.GOFLAGS = -json’ parameter to the build configuration.

Token-based authentication

In addition to basic HTTP authentication, TeamCity now supports authentication based on permanent access tokens. With tokens, you don’t need to expose a user login and password in scripts. Instead, you can send a token in an authentication header when querying the TeamCity API. You can generate new tokens in TeamCity or delete them any time.

New documentation website

To create a better experience and ensure a common look and feel across the documentation of all JetBrains products, we moved TeamCity documentation to a new platform. The documentation for previous versions stays in Confluence.

The Plugin Development Help is now residing on a separate site. Its source files are moved to the public GitHub repository so our community can contribute.

The detailed feature description and the list of fixes are available in our Release Notes.

As usual, the new release changes the TeamCity data format and, since the version 2019.1 is still in development, we recommend installing it on a trial server.

You are welcome to try the new EAP build and share your feedback on our forum or tracker.

Happy building!

This entry was posted in EAP. Bookmark the permalink.

5 Responses to TeamCity Kanpur 2019.1 EAP3 is here

  1. Lior Tal says:

    build artifacts improvements is nice! what about async artifact publishing?

    e.g: a build configuration is made of 10 steps, each creates an artifact. i can upload the artifact of step 1 already while executing step 2, improving the overall build time.

  2. sdc says:

    The new documentation site needs work. It looks like the font styles are broken on several places text is showing up as __Words to make bold__. (Example is basic TC concepts section: https://www.jetbrains.com/help/teamcity/2019.1/continuous-integration-with-teamcity.Html)

    The “See Also” section can be better formatted, to be fair the formatting wasn’t much better on the old site. On some pages the “See also” links show up as a single wrapped paragraph. (Example: https://www.jetbrains.com/help/teamcity/2019.1/msbuild.html)

    “Important” or “Notable” information weirdly shows up outside of the table instead of in the cell. This is awkward and it took me a minute to figure out the light bulb marked the row the information is in reference too. I might not of even figured it out expect that I looked at the confluence site for reference. (Example in msbuild table: https://www.jetbrains.com/help/teamcity/2019.1/msbuild.Html)

    The “Code” font style needs work. Especially for multi-line code blocks. The style has no ending paragraph margin so the next paragraph is too close. The font isn’t distinct enough and looks like bold text. (Example Build properties section: https://www.jetbrains.com/help/teamcity/2019.1/gradle.Html)

    After playing with the new site for a few minutes I find I like the confluence documentation better
    – Site comments on each page were public.
    – Page version history was available.
    – Exporting was built in, For the few times I have done this I guess I can use print to PDF from my browser.

    I do look forward to the new version of TC especially the revamped dashboard and the changes artifact publishing.

  3. Julia Alexandrova says:

    Hi Sdc, thanks for so much for taking time to report all the issues you noticed. We’re working on fixing them.

    As to exporting, Print to PDF is a way to go.

    If you have a comment, you can send us your feedback using the “Was this page helpful?” form at the bottom.

    Could you elaborate in the page history? Why is it important for you?

    Thanks very much in advance!

  4. sdc says:

    I think on the confluence site I was able to subscribe to pages. When the page was changed I would get notified. The notification wouldn’t show me what changed but I was able to use the history to see the differences.

    For example I know I did this with the service message page. When I first started using TC this concept was difficult to understand how to use it. I subscribed to the page. I got notifications about it being updated. To figure out what was new I used this feature. Sometimes by seeing what was changed in the documentation helped give additional context to how to use the TC feature.

Leave a Reply to Julia Alexandrova Cancel reply

Your email address will not be published. Required fields are marked *