Include build environment in Jenkins

[ghost]

In allure2 it is not implemented although it was present in allure1. It would be good to have it back.

[vbragin]

@da-yaroslav-orel Please explain the problem more detailed.

[ghost]

@vbragin In Allure2 'include build environment' checkbox doesn't work. So when report is generated 'Environment' section on landing page is empty.

[marvelfrozen]

Any updates on this issue?
I assume there's some technical problem implementing this feature on allure2.
Meanwhile, any workaround that we can use for now?

Edit: I try putting environment.properties in /allure-results and it shows up in the report. It's good enough for now I guess.

[kemuning]

@gavrilfb how did you copy your environment.properties into /allure-result ? Is it via Jenkins or in you specify in your pom.xml ?

[marvelfrozen]

@kemuning There are several ways to do that. If you are using Jenkins, you could just put a pre-build step calling copy command. Or you could just create some codes to generate the files in your source code.

[usmichael]

@gavrilfb How did you managed it to work?
I'm using allure v2.6 and I'm forcing the environment.properties into allure-results in a shell step before running the post-build allure action, but data is not appearing in the report. When inspecting the allure-results workspace the file is there indeed and with my content but searching for it in the allure-report the widgets/environment.json is empty.

[marvelfrozen]

@usmichael what is your environment.properties file structure? i use standard .ini format key = value

also, the properties will show unordered in the reports. if you found any ways to make it ordered please share it.

[usmichael]

Hey @gavrilfb,

File content is as so:

my.properties.browser=SAFARI
my.properties.url=http://yandex.ru