RestAssured.baseURI未用自定义值，Jenkins测试报连接拒绝求助

Let's break down your two problems and walk through actionable fixes for each:

1. RestAssured.baseURI Not Using Custom Config Value #

If your code is picking up the default baseURI instead of your custom setting, here are the most likely fixes:

• Check the timing of your configuration: Make sure you set RestAssured.baseURI before any API request is executed. For test frameworks like JUnit 5, use @BeforeEach (or @Before for JUnit 4) to set the baseURI in a setup method, not in a static block that might run too early or get overridden. Example:

  @BeforeEach
  void setup() {
      RestAssured.baseURI = "https://your-custom-url.com";
  }
  

• Look for accidental overrides: Search your codebase for other instances where RestAssured.baseURI is set—sometimes helper classes or other test setup methods might reset it after your initial config.
• Verify configuration file conflicts: If you're using a rest-assured.properties file (either in src/test/resources or a custom location), make sure it doesn't have a baseURI property that's overriding your code-based setting. RestAssured loads properties from this file automatically by default.
• Use explicit configuration builders: For more control, try setting the baseURI via the config builder to ensure it's applied correctly:

  RestAssured.config = RestAssured.config().baseURI("https://your-custom-url.com");
  

2. Jenkins Connection Refused Error (Local Works, Jenkins Fails) #

Connection refused errors in Jenkins when local tests pass almost always relate to network accessibility between the Jenkins environment and your target service. Here's how to debug and fix this:

• Confirm target service is reachable from Jenkins server:
  • Log into your Jenkins server (or the agent running the tests) and run a test command to check connectivity:
    • For HTTP port 80: curl http://your-target-ip:80 or telnet your-target-ip 80
    • For SSH port 22: ssh your-target-user@your-target-ip or telnet your-target-ip 22
  • If these commands fail, the problem is network-level:
    • Check firewall rules on the target server to ensure ports 80/22 are open to the Jenkins server's IP.
    • Verify your target service isn't bound only to 127.0.0.1 (localhost)—if it is, Jenkins (running on a different machine/container) can't reach it. Update the service to bind to 0.0.0.0 or the server's public/private IP.
• Check for Jenkins proxy settings: If Jenkins is configured to use a global proxy, it might be routing your test requests through the proxy instead of directly to your target service. Disable the proxy temporarily (or add your target URL to the proxy bypass list) to test this.
• Ensure target service is running during Jenkins tests: If you're starting the service as part of your local test workflow but not in Jenkins, make sure your Jenkins pipeline includes steps to start the service before running tests, and verify it's fully initialized before test execution.
• Review the full error context: The stack trace you shared shows an HTTP connection failure—double-check that your test is using the correct target IP/hostname in Jenkins (sometimes local tests use localhost which won't work in Jenkins if the service isn't running on the Jenkins agent).

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