Run the agentInstaller.exe Windows Installer and follow the installation instructions. Click the Install Build Agents link and select MS Windows Installer to download the installer. Just to try what happens, since the version is actually 2.0.4 now and I don’t have another agent to try on, I will briefly bump up the version requirement to 2.0. In the TeamCity Web UI, navigate to the Agents tab. My final requirement will look like this (ensuring that the Pester version will be at least 2.0.4): You can even see that you’ll get some “intellisense” for the parameter you just created. Now head over to the build configuration that wishes (has a requirement) on the Pester module and add an agent requirement: Now, the agent will now pick up that change automatically and you can verify it through the agent properties using the TeamCity admin UI: I think an environment variable is correct since I’ve installed Pester 2.0.4 globally on the server. Note: That’s my way of indicating that Pester is now version 2.0.4 on this server (a bit manual but hey?). I’ve added a parameter at the bottom there: On the TeamCity server go into the agent properties file ( C:\ TeamCity \buildAgent\conf\ on my server). There are a lot built-in requirements that you can use but since this is a custom requirement I decided to implement it like this: My Teamcity configs are default (Ive changed nothing there). Here are parts of log files: Also Ive disabled firewall to make sure this doesnt affect Teamcity. My OS is Debian 圆4, oracle jdk8 is installed and env variables are ok. PSGet knows nothing about versions but I know that the code on GitHub that PSGet will pull down is of version 2.0.4 state. Ive installed Teamcity v9 on my VPS and I have some trouble with it: its not working at all. I’ve just updated Pester to version 2.0.4 (not yet released on nuget at the time of me writing this post though) via PSGet on the TeamCity server. This is the result of that “investigation”, enjoy! Before moving to the cloud, the TeamCity server was installed in one of the offices while build agents were also running on-premises in the same office. As is fairly common for game development companies, Playrix operates huge repositories of up to 50 GB each and generates large artifacts. So I decided to investigate how I could overcome these obstacles. The Playrix TeamCity server runs in the cloud. the module was actually installed on the server.Currently supported combinations of the server host platform and targets for build agents are: from the Unix-based TeamCity server build agents can be installed to Unix hosts only (via SSH). The downside of this approach was that I didn’t have a great story for knowing whether: TeamCity provides functionality that allows installing a build agent to a remote host. The reason was that I used PSGet to install a PowerShell module ( Pester) onto the TeamCity agent server, i.e. 9.x) - license 1 Year Upgrade Subscription - 1 additional agent Compare similar Multiple Build Agents Load statistics matrix. While I was working on another blog post I got to thinking about agent requirements.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |