Hi @Dheeraj Singla,
I'm not familiar with Selenium, but I see that you are not actually using the service you have defined in any step. Additionally, the definitions: keyword should be at the same level as pipelines: (I am not sure if the indentation looks the same in your yml file, or if it got messed up here during copy-paste).
If selenium is used in the first step, you could try a yml as follows:
image: maven:3.6.0
pipelines:
default:
- parallel:
- step:
name: Build and Test
services:
- chrome
caches:
- maven
script:
# - mvn -B verify
- ls -l /opt/atlassian/pipelines/agent/build/chromedriver_win32/
- mvn test
after-script:
# Collect checkstyle results, if any, and convert to Bitbucket Code Insights.
- pipe: atlassian/checkstyle-report:0.3.0
- step:
name: Security Scan
script:
# Run a security scan for sensitive data.
# See more security tools at https://bitbucket.org/product/features/pipelines/integrations?&category=security
- pipe: atlassian/git-secrets-scan:0.5.1
definitions:
services:
chrome:
image: selenium/standalone-chrome
Just to give you some context, Pipelines builds run in Docker containers. For every step of your build, a Docker container starts (the build container) using the image you have specified in your bitbucket-pipelines.yml file (in your case maven:3.6.0). If you use a service for a step, then a second Docker container will start for the service (using the image you have specified for the service) which will share a network adapter with your build container and open its ports on localhost.
You can have a look at the following guide if you would like to debug this locally with Docker (For step 3, make sure to check Testing with build services before starting the build container locally):
Kind regards,
Theodora
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.