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
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.
BStackLogger.warn('Skipping buildIdentifier as buildName is not passed.')
return
}
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
Thereisnorelevantoutputforthisbuginlogs.
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
The text was updated successfully, but these errors were encountered:
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).
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.
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.
Have you 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?
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.
webdriverio/packages/wdio-browserstack-service/src/launcher.ts
Lines 701 to 705 in fa5f02f
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
Code of Conduct
Is there an existing issue for this?
The text was updated successfully, but these errors were encountered: