如何为TeamCity添加参数以修改pom.xml中测试线程配置？

Alright, let's figure out how to add this functionality to TeamCity so you can switch between single and multi-threaded test runs by adjusting the Maven Surefire config in your pom.xml. I've done similar setups before, so here's a straightforward, actionable approach:

First, we'll turn those fixed Surefire settings into overridable Maven properties. This lets TeamCity pass in values at build time instead of editing the pom directly.

Update your pom.xml's profile section like this:

<profile>
  <id>test-thread-profile</id>
  <build>
    <plugins>
      <plugin>
        <artifactId>maven-surefire-plugin</artifactId>
        <version>2.22.0</version>
        <configuration>
          <perCoreThreadCount>${surefire.perCoreThreadCount}</perCoreThreadCount>
          <threadCount>${surefire.threadCount}</threadCount>
          <parallel>${surefire.parallel}</parallel>
          <!-- Keep your existing excludes block here -->
        </configuration>
      </plugin>
    </plugins>
  </build>
</profile>

Then add default values in the <properties> section of your pom (so builds work normally without TeamCity params):

<properties>
  <!-- Default multi-threaded config -->
  <surefire.perCoreThreadCount>false</surefire.perCoreThreadCount>
  <surefire.threadCount>3</surefire.threadCount>
  <surefire.parallel>classes</surefire.parallel>
</properties>

Now we'll set up TeamCity to let users toggle between single/multi-threaded modes:

1. Go to your TeamCity build configuration and navigate to the Parameters tab.
2. Add these three parameters (set them as "Configuration Parameters" or "System Properties"—system properties work directly with Maven):
   • -Dsurefire.perCoreThreadCount: Use a dropdown list with options true/false, default to false
   • -Dsurefire.threadCount: Use a dropdown or text field with options like 1 (single-thread) / 3 (multi-thread default), default to 3
   • -Dsurefire.parallel: Use a dropdown with options none (single-thread) / classes (multi-thread), default to classes

Make sure your Maven build step uses the profile we created, so the property overrides take effect:

• In your build step's Goals field, add the profile to your command, e.g.:

  clean test -Ptest-thread-profile
  

• Single-threaded run: When selecting this mode, TeamCity will pass:
  -Dsurefire.parallel=none -Dsurefire.threadCount=1
  This disables parallel execution entirely, forcing tests to run one after another.
• Multi-threaded run: Use the default values or let users adjust the threadCount to their needs—TeamCity will pass the selected values to override the pom's defaults.

内容的提问来源于stack exchange，提问作者NiG1lisT