![]() Have a "10,000-foot look" at TeamCity, and the supported IDE's, frameworks, version control systems and means of monitoring. TeamCity Supported Platforms and Environments If you have new feature suggestions, error reports, please report them to the TeamCity Issue Tracker. If you have any questions, you are welcome to contact our developers at the TeamCity Community Center forums. To get information about publicly available TeamCity plugins, please refer to the TeamCity Plugins space. If you're using TeamCity earlier than 6.0, you can find corresponding documentation here: Documentation for previous TeamCity versions On the Official TeamCity Blog and TeamCity Developers Blog you will find the latest news from our team, handy feature's descriptions, usage examples, tips and tricks. To get general information about TeamCity and its features, please visit TeamCity Official Site. Where to Find More Information and Send Feedback If you're new to TeamCity it is recommended to familiarize yourself with these concepts. This section is intended to give you basic understanding of TeamCity-specific terms, like build configuration, project, build queue, etc. The Administrator's Guide contains essential instructions on configuring and maintaining the TeamCity server and build agents, working with projects and build configurations, managing users and their permissions, integrating TeamCity with other tools, and more. From this section you will learn how to subscribe to TeamCity notifications, view how your changes have affected different projects, view current problems, use TeamCity search. TeamCity User's Guide is for everyone who uses TeamCity. Review upgrade notes and see the Upgrade section if you are upgrading your existing TeamCity instance. Refer to the Installation section if you are installing TeamCity for the first time. Documentation Space Structureįor your convenience, the documentation space is divided into following sections: Installation and Upgrade To familiarize yourself with them, please refer to What's New in TeamCity 6.0.Īlso, take a look on the list of Supported Platforms and Environments and on their visual representation. If using a continuous integration tool different to TeamCity, as long as it supports any of the build tools, or calling command line tools, compiling Kotlin and automating things as part of a CI process should be possible.TeamCity 6.0 contains a bunch of new features and improvements. With that, our project should now build and produce the corresponding artifacts. The final step is to define the actual compilation of the project, which uses the standard IntelliJ IDEA Runner Type. Therefore, you need to define it as a system variable. However, this value needs to be defined in TeamCity (and can be set to any value). The runner will set the value for the property .BUNDLED to the correct one based on the path settings from the IntelliJ IDEA project. Download that meta-runner and import it from the TeamCity user interface Setup Kotlin compiler fetching stepīasically this step is limited to defining the Step Name and the version of Kotlin you need. The meta-runner for Kotlin is available on GitHub. They are very easy and powerful way to introduce custom Runners without the need to write plugins. If not familiar with the concept of TeamCity meta-runners, check the documentation. You may need to download the specific version of the Kotlin plugin and install it on TeamCity.įortunately, there is a meta-runner already available that takes care of most of the manual work. If using IntelliJ IDEA build system with TeamCity, make sure that the version of Kotlin being used by IntelliJ IDEA is the same as the one that TeamCity runs. The only difference being that the Runner Type would be Ant or Maven respectively. If using Ant or Maven, the same configuration applies. Since all the dependencies required for Kotlin are defined in the Gradle file, nothing else needs to be configured specifically for Kotlin to run correctly. For example, if using Gradle, simply define the required parameters such as the Step Name and Gradle tasks that need executing for the Runner Type. All that is needed is to define the Build Step. If using Ant, Maven or Gradle, the setup process is straightforward. Where there are some minor requirements and differences is when using the internal build system of IntelliJ IDEA, which is also supported on TeamCity. Kotlin works with different build tools, so if you're using a standard tool such as Ant, Maven or Gradle, the process for setting up a Kotlin project is no different to any other language or library that integrates with these tools. For more information and basics of TeamCity please check the Documentation page which contains information about installation, basic configuration, etc. On this page, you'll learn how to set up TeamCity to build your Kotlin project. Kotlin and continuous integration with TeamCity ![]()
0 Comments
Leave a Reply. |