[🐛 Bug]: BrowserStack build identifier is not set when BROWSERSTACK_BUILD_NAME environment variable is set about webdriverio

[christian-bromann]

buildIdentifier: '${BUILD_NUMBER}'

It seems like you are also setting the buildIdentifier in your capabilities here. Can you remove this entry and try again? Also can you verify that your environment variables were set correctly by printing them out via e.g. console.log(process.env. BROWSERSTACK_BUILD_NAME).

[kwiniarski]

I think I have tried all combinations already. But checked them again. When environment variables are set then adding buildIdentifier to the service options or capabilities options or both at the same time has no effect. My build name in BrowserStack has no number.

But when I remove environment variables and hardcode build name in configuration, then setting buildIdentifier in service options works as expected. All my builds are numbered in BrowserStack.

[christian-bromann]

@kwiniarski can you provide a minimal reproducible example?

[kwiniarski]

I can't post the repo where I have this, but I will try to extract the minimal code. I think it will be helpful because I also have another potential bug with BrowserStack there.

[kwiniarski]

I have created repository with simple example that reproduces described issue: https://github.com/kwiniarski/wdio-browserstack-stencil.
Steps to reproduce are in the README.md

[wdio-bot]

Thanks for reporting!

We greatly appreciate any contributions that help resolve the bug. While we understand that active contributors have their own priorities, we kindly request your assistance if you rely on this bug being fixed. We encourage you to take a look at our contribution guidelines or join our friendly Discord development server, where you can ask any questions you may have. Thank you for your support, and cheers!

[christian-bromann]

@kwiniarski thanks for providing an example. We would appreciate any help identifying if this is a bug related to WebdriverIO and potential fixes for this. Cheers!