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

Have you read the Contributing Guidelines on issues?

• I have read the Contributing Guidelines on issues.

WebdriverIO Version

8.35.1

Node.js Version

v20.9.0

Mode

Standalone Mode

Which capabilities are you using?

[
  {
    browserName: 'Chrome',
    'bstack:options': {
      projectName: 'Pinta',
      buildName: 'LOCAL',
      consoleLogs: 'verbose',
      networkLogs: true,
      local: true,
      debug: true,
      buildTag: 'desktop',
      browserVersion: '120.0',
      os: 'Windows',
      osVersion: '11',
      wdioService: '8.35.1',
      buildIdentifier: '${BUILD_NUMBER}'
    }
  },
  {
    browserName: 'Safari',
    'bstack:options': {
      projectName: 'Pinta',
      buildName: 'LOCAL',
      consoleLogs: 'verbose',
      networkLogs: true,
      local: true,
      debug: true,
      buildTag: 'desktop',
      browserVersion: '15.6',
      os: 'OS X',
      osVersion: 'Monterey',
      wdioService: '8.35.1',
      buildIdentifier: '${BUILD_NUMBER}'
    }
  }
]

What happened?

I'm using WebdriverIO with BrowserStack service and I have noticed that when I set build name through BROWSERSTACK_BUILD_NAME environment variable, then setting build identifier has no effect. Digging a little into the code I have found this condition in launcher.ts which effectively terminates processing of build identifier when BROWSERSTACK_BUILD_NAME is set.

https://github.com/webdriverio/webdriverio/blob/fa5f02f24b64372d2791814bde1306788319e30e/packages/wdio-browserstack-service/src/launcher.ts#L701-L705

What is your expected behavior?

No response

How to reproduce the bug.

Just set up BROWSERSTACK_BUILD_NAME variable and then run tests using browserstack-service. In BrowserStack dashboard you will see that following build are not numbered. All test sessions are appended to the one, already existing build.

Relevant log output

There is no relevant output for this bug in logs.

Code of Conduct

• I agree to follow this project's Code of Conduct

Is there an existing issue for this?

• I have searched the existing issues