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
It is possible (although not necessary) to explicitly work with docker networks. This library supports the automatic creation and removal of a bridge network with a unique name.
51
+
52
+
### How
53
+
54
+
`withZalenium` accepts now an optional network name the Zalenium container can attach to the given network. Conveniently a docker network can be created with this pipeline step which provides the dynamically created network name.
Starts a temporary zalenium server, that stores videos of the selenium tests in the workspace.
1
+
Starts a temporary Zalenium server that stores videos of the selenium tests in the workspace.
2
2
3
3
Requires Docker!
4
4
5
5
(optional) Parameters:
6
6
7
-
- seleniumVersion - version of the "elgalu/selenium" docker image
8
-
- zaleniumVersion - version of the "dosel/zalenium" docker image
9
-
- zaleniumVideoDir - workspace relative path where the videos are stored
7
+
- seleniumImage - the full name of the selenium image name including the registry. Defaults to 'elgalu/selenium' from hub.docker.com. The selenium image is used by Zalenium.
8
+
- seleniumVersion - version of the selenium docker image
9
+
- zaleniumImage - the full name of the zalenium image name including the registry. Defaults to 'dosel/zalenium' from hub.docker.com.
10
+
- zaleniumVersion - version of the zalenium docker image
11
+
- zaleniumVideoDir - path where the videos are stored, relative to the Jenkins workspace.
10
12
- debugZalenium - makes the zalenium container write a lot more logs
13
+
- sendGoogleAnalytics - if true this will send analytic data to Google/Zalando
0 commit comments