![]() ![]() Note that some other (usually older) guides recommend also setting -XX:MaxPermSize: this is no longer needed! My First Agent Around 4GB and above, it starts becoming necessary to also include a value for -XX:ReservedCodeCacheSize= but smaller deployments don't need this.įor more detail, checkout the documentation on configuring TeamCity memory settings. Here, I'm telling it that the JVM should max out at 750MB RAM, which is JetBrains's recommendation for minimum/small deployments. You'll see the TEAMCITY_SERVER_MEM_OPTS option above TeamCity veterans will recognise it as how TeamCity's underlying JVM picks up its memory configuration, but if you're new to TeamCity, or the JVM (like me), it's probably a little confusing.Įssentially (and this is an over-simplification) TeamCity relies on the JVM for controlling it's maximum RAM usage, and the JVM uses the values you specify in the TEAMCITY_SERVER_MEM_OPTS environment variable. The volume/directory you map into datadir will be used to hold TeamCity's configuration and project data (likewise for the self-explanatory logs volume). '/opt/teamcity/log:/data/teamcity/logs' '/opt/teamcity/data:/data/teamcity_server/datadir' Image: 'jetbrains/teamcity-server' # the official JetBrains image Next, in my new docker-compose.yml file, I start by defining the TeamCity server: version: '2' I'll be assuming you're running on a Linux box, but these commands should be pretty easy to co-opt to any other OSes (just update paths as appropriate).įor my setup, I created a simple directory structure under /opt to hold my server and agent data: /opt/teamcity/ ![]() Fortunately, JetBrains have now started publishing official images for both the TeamCity Server and Agent components, so today we'll be setting up a simple TeamCity environment using Docker Compose.Įven better, JetBrains offers TeamCity Professional completely free! No reason not to try it out. Recently, I needed a quick TeamCity build environment to test some new development changes. Open the Overview tab and see which tests failed and why.Docker is an incredibly powerful tool for building networks of interconnected components without worrying about dependencies, conflicts or machine provisioning. Now you can run the build using the Run button. Now the TeamCity build configuration will fetch tests from the testcafe-ci-demo repo each time it runs. In the Authentication Settings section, select Password as the Authentication Method, enter your credentials and click Create. A drop-down list of GitHub repos associated with your account will open. In the Fetch URL field, click the GitHub logo. On the VCS Roots page, click Attach VCS root. Go to the configuration parameters and click Version Control Settings. Next, attach a VCS root to the build configuration. In the Register a new OAuth application dialog, specify the application name, homepage URL and authorization callback URL as they are provided by TeamCity and click Register application.Ī page with client application ID and secret will open.Ĭopy and paste them to TeamCity and click Save. Select as the Connection type and click Register TeamCity to set up OAuth authentication with GitHub. The Add Connection dialog will be invoked. On the Connections page, click Add Connection. Open project settings and click Connections. Parameters used in this example specify Google Chrome as the target browser, tests as the folder that contains test fixtures and TeamCity reporter as a plugin used to output test run reports.įirst, you will need to create a connection with. Type testcafe into the Command executable box and add the following arguments in the Command parameters field: chrome tests/**/* -r teamcity. In the Run parameter, select Executable with parameters. Optionally, specify a name for this step. In the Runer type field, select Command Line. Configure this step to run TestCafe using the command line. On this page, click the Add build step button. First, select Build Steps from the left menu. In the configuration settings, add a build step that runs TestCafe. Ĭlick the Edit Configuration Settings link. Ĭreate a new build configuration or open an existing one as described in the TeamCity documentation . You can find a list of supported VCS in the TeamCity documentation . If you use a different version control system, make sure TeamCity supports it. We will fetch test code from a GitHub repository: testcafe-ci-demo . The reports will be presented in the TeamCity UI allowing you to analyze the results with its built-in features. The testcafe-reporter-teamcity plugin enables TestCafe to output test run results in the TeamCity format. npm install -g testcafe testcafe-reporter-teamcity Prerequisitesīefore starting this tutorial, install TestCafe and the TeamCity reporter plugin. This topic describes how to use TestCafe with TeamCity . TestCafe is easy to set up with most modern CI systems. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |