Manish Upadhyay comments

Results 5 comments of


                                            Manish Upadhyay

When using zenika/alpine-chrome:with-chromedriver docker image then in GitLab CI ChromeDriver was started successfully. is display but it get stuck and do nothing

Can someone please look into this and help me to resolve this issue? As per my understanding I think zenika/alpine-chrome:with-chromedriver docker image starting chrome driver 121 but chrome has now...

When using zenika/alpine-chrome:with-chromedriver docker image then in GitLab CI ChromeDriver was started successfully. is display but it get stuck and do nothing

@zigarn zigarn Can you please take a look at this?

When using zenika/alpine-chrome:with-chromedriver docker image then in GitLab CI ChromeDriver was started successfully. is display but it get stuck and do nothing

Hey @zigarn thanks for your response, please find below minimal gitlab ci and docker files **.gitlab-ci.yml** ```yaml image: internal/java-builder:17 variables: MAVEN_CLI_OPTS: "-s .m2/settings.xml --batch-mode" MAVEN_OPTS: "-Dmaven.repo.local=.m2/repository" CONTEXT: "" ENVIRONMENT: ""...

When using zenika/alpine-chrome:with-chromedriver docker image then in GitLab CI ChromeDriver was started successfully. is display but it get stuck and do nothing

@zigarn when I use the entrypoint above as you mentioned then the mvn is not found message is displayed #... SmokeTest: stage: SmokeTest image: name: zenika/alpine-chrome:with-chromedriver entrypoint: [""] #...

When using zenika/alpine-chrome:with-chromedriver docker image then in GitLab CI ChromeDriver was started successfully. is display but it get stuck and do nothing

@zigarn can you please give me an example with my above gitlab ci file?