Gradle+jUnit4环境下Allure代理配置及报告生成问题求助

Hey there! I see you're hitting a proxy authentication roadblock when trying to generate Allure reports with Gradle—even though your proxy works for other build tasks, the downloadAllure task keeps throwing that frustrating HTTP/1.1 407 Proxy Authentication Required error. Let's break down how to fix this step by step.

First: Verify Your Gradle Proxy Configuration #

First, make sure your gradle.properties includes complete proxy settings with authentication (since 407 means the proxy is asking for credentials your task isn't providing). Add these lines if you haven't already:

# HTTP Proxy Settings
systemProp.http.proxyHost=your-proxy-server.com
systemProp.http.proxyPort=8080
systemProp.http.proxyUser=your-username
systemProp.http.proxyPassword=your-password

# HTTPS Proxy Settings (Allure downloads from HTTPS sources)
systemProp.https.proxyHost=your-proxy-server.com
systemProp.https.proxyPort=8080
systemProp.https.proxyUser=your-username
systemProp.https.proxyPassword=your-password

# For NTLM proxies (common in corporate environments)
systemProp.http.auth.ntlm.domain=your-corporate-domain
systemProp.https.auth.ntlm.domain=your-corporate-domain

Force Allure Plugin to Inherit System Proxy Settings #

The Allure Gradle plugin's downloadAllure task might not automatically pick up your system proxy properties. You can explicitly pass these settings to the task in your build.gradle:

tasks.named('downloadAllure') {
    // Pass all system properties (including proxy config) to the download task
    systemProperties System.getProperties()
}

Upgrade the Allure Gradle Plugin #

You're using an older version of the Allure Gradle plugin (2.5), which might have bugs related to proxy handling. Try upgrading to a newer, more stable version:

1. Update the buildscript dependency:

   buildscript {
       repositories { jcenter() }
       dependencies { classpath "io.qameta.allure:allure-gradle:2.11.2" } // Latest compatible version as of now
   }
   

2. Adjust your Allure core version to match (optional but recommended):

   allure {
       version = '2.24.0' // Align with plugin compatibility
       // Keep your existing config (aspectjweaver, resultsDir, etc.)
   }
   

Manual Workaround: Skip Automatic Download #

If all else fails, you can bypass the proxy entirely by using a local copy of the Allure Command Line tool:

1. Download the Allure zip package matching your configured allure.version
2. Extract it to a local folder (e.g., ./tools/allure)
3. Update your allure config in build.gradle to use the local executable:

   allure {
       // Other existing config...
       // Point to the local Allure binary
       commandline = file('./tools/allure/bin/allure') // Use allure.bat for Windows systems
   }
   

Quick Dependency Cleanup #

Also, note that your current Allure dependency is for Allure 1.x (ru.yandex.qatools.allure:allure-junit-adaptor:1.5.4), but you're using the Allure 2.x plugin. This can cause conflicts. Replace it with the Allure 2.x JUnit 4 adaptor:

dependencies {
    // Remove the old 1.x adaptor
    // compile "ru.yandex.qatools.allure:allure-junit-adaptor:1.5.4"
    // Add Allure 2.x JUnit 4 dependency
    testImplementation 'io.qameta.allure:allure-junit4:2.24.0'
    // Keep your other dependencies (junit, aspectjweaver, etc.)
}

That should resolve the proxy authentication issue and get your Allure reports generating properly!

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