You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What Operating System are you using (both controller, and any agents involved in the problem)?
controller: centos 6.4
agent: windows 10
Reproduction steps
configure your jenkins controller to archive all build artifacts on an artifactory instance using the aritfactory artifact manager plugin.
create a simple job which produces allure result files, or have allure results files somewhere on the agent (a sample can be obtained on the internet).
run the allure step from jenkins on the result folder.
Expected Results
allure report should appear in jenkins.
alure-result.zip file should appear in jenkins build artifacts, and saved in the artifactory.
Actual Results
the allure report appears on the build page in jenkins as expected.
the allure-results.zip file resides in the ./archive folder of the build, and does not appear in the build page gui.
Anything else?
this issue might be related to the artifactory artifact manager archive implementation, but the behavior of the allure plugin is changed once the artifactory artifact manager plugin is installed and configured, so it might be also a missing end case of the current plugin. other jobs using the archive artifacts mechanism work properly (files are archived in the artifactory, and appear on the job page in jenkins).
Are you interested in contributing a fix?
No response
The text was updated successfully, but these errors were encountered:
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
controller: centos 6.4
agent: windows 10
Reproduction steps
Expected Results
Actual Results
Anything else?
this issue might be related to the artifactory artifact manager archive implementation, but the behavior of the allure plugin is changed once the artifactory artifact manager plugin is installed and configured, so it might be also a missing end case of the current plugin. other jobs using the archive artifacts mechanism work properly (files are archived in the artifactory, and appear on the job page in jenkins).
Are you interested in contributing a fix?
No response
The text was updated successfully, but these errors were encountered: