Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to check visualReport on Jenkins remotely #57

Closed
Jun-Zhu-Trend opened this issue Jun 15, 2020 · 4 comments
Closed

How to check visualReport on Jenkins remotely #57

Jun-Zhu-Trend opened this issue Jun 15, 2020 · 4 comments

Comments

@Jun-Zhu-Trend
Copy link

Jun-Zhu-Trend commented Jun 15, 2020

Describe the bug
The image path is absolute path which is embedded when created, and when using Jenkins HTML report plugin, it cannot show the report well , how can I configure to show it on Jenkins server correctly ?

1

The path "href="C:\ci-l10n\workspace\I18N\Test\Jun_Win_Test\regression\base\VisualDiffGoogle\img1.png"" is that path on my jenkins node build machine.

Here is my configuration on Jenkins server:
2

I run command like below:
(cd <root folder where *.robot exists, ex:>C:\ci-l10n\workspace\I18N\Test\Jun_Win_Test\regression)
robot -d results -v images_dir:base .

Any ideas ?
thanks a lot for your help.

@Jun-Zhu-Trend
Copy link
Author

Jun-Zhu-Trend commented Jun 15, 2020

I use one alternative way to use another python script to update the report HTML by using relative path in the report HTML, and it works, like below:
"href=".\base\VisualDiffGoogle\img1.png"
Since it needs me to write another script to update the report manually, I am not sure whether there is a better way to generate the visualreport directly by using relative path inside it.

@jessezach
Copy link
Owner

@Jun-Zhu-Trend Thanks for using the library.
I went through the code and it does look like absolute path is used for baseline folder. Could you please confirm if the actual and the diff images also contain absolute path in your local system?

@jessezach
Copy link
Owner

jessezach commented Jun 15, 2020

@Jun-Zhu-Trend For the time being, instead of using your own script you can generate the report again with relative paths by using the following command instead,
reportgen --baseline=base --results=results . Just pass relative paths to baseline directory and results/output directory. This should solve the problem with absolute path. Let me know if this does it.

@Jun-Zhu-Trend
Copy link
Author

Jun-Zhu-Trend commented Jun 15, 2020

I just tried to genereate the report again after run with : reportgen --baseline=base --results=results .
it works,
thanks a lot.

by the way, to comment your question above:
please confirm if the actual and the diff images also contain absolute path in your local system?

Yes, all the path are generated with absolute path with command : robot -d results -v images_dir:base .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants