Vladimir Sitnikov

Ah, the plugin calls Allure binary as a regular executable, so we probably want to expose `environment variables` for launching the executable.

@myniva , `doesObjectExist` is a separate request which goes over the internet. So if the same thing is implemented as a single network call, then it should be faster. Note:...

Hi, I believe https://github.com/allure-framework/allure-gradle/pull/61 fixes the issue as the plugin no longer adds dependencies to `testCompile`. Please feel free to try it and provide feedback

Resolved in #61

@baev , is `allureJava` adapter always released together with `allure-commandline`? If that is the case, we could use `allureJavaVersion.convention(allure.version)` so `allureJavaVersion` is using `allure.version` by default. WDYT? At the same...

I believe the issue is fixed in https://github.com/allure-framework/allure-gradle/pull/99

The CI says ``` Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Could not transfer artifact org.codehaus.gmaven.runtime:gmaven-runtime-loader:pom:1.5-jenkins-3 from/to azure (https://repo.azure.jenkins.io/public/): repo.azure.jenkins.io:443 failed to respond ``` and I consider that an unrelated failure.

@hagzag , what do you mean by that?

Implemented in https://github.com/jenkinsci/tikal-multijob-plugin/pull/140

This PR fixes the issue: https://github.com/jenkinsci/tikal-multijob-plugin/pull/142