One of our recent project requited the setup of a new Jenkins on an AWS Workspace instance with Windows 7 OS. The task was not particularly hard, just a basic setup for fetching and compiling a repo, building and running Selenium tests.
After installing and setting up the service version of the Jenkins everything was fine: the build was successful and the logs appeared on the console as it was expected. After a while a strange thing happened: no browsers appeared although the logs confirmed that they were started, all the tests were running correctly and all of them passed at the end of the run.
We did not really understand what happened, but after a short discussion, one of our colleague mentioned that he experienced that behavior earlier in a similar setup and he solved the issue with using the .war version of Jenkins instead of the service one. After downloading and starting the .war version we started the same job again and this time all the browsers appeared on the expected way.
After googling a while we figured out that the Jenkins service was actually installed into the system user, not into ours so all the browsers were started there instead of on our user’s desktop. In the case when we started it as a .war the application was started where we wanted and all the browsers were visible.
If you already have a Jenkins set up as a service but want to run it as a .war, just simply start the .war file. If the default .jenkins folder was set up as home folder, the standalone version will find that and you can continue with the jobs without further configuration. In case if you changed the home folder just target the same, all the configurations will be available.
Share your experience! Feel free to comment or contact us!
Similar Posts from the author:
- Getting started with Webdriver python guide
- Getting started with Android automation testing
- Event logging with aspects in automated testing
- Overview of automated testing
- Graphwalker – Guards and actions
Recent Comments