Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[test] Run Browserstack tests on master only #578

Merged
merged 1 commit into from
Sep 4, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion test/karma.conf.js
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,7 @@ const webpack = require('webpack');
const CI = Boolean(process.env.CI);
// renovate PRs are based off of upstream branches.
// Their CI run will be a branch based run not PR run and therefore won't have a CIRCLE_PR_NUMBER
const isPR = Boolean(process.env.CIRCLE_PULL_REQUEST);

let build = `Base UI local ${new Date().toISOString()}`;

Expand All @@ -21,7 +22,7 @@ const browserStack = {
// Since we have limited resources on BrowserStack we often time out on PRs.
// However, BrowserStack rarely fails with a true-positive so we use it as a stop gap for release not merge.
// But always enable it locally since people usually have to explicitly have to expose their BrowserStack access key anyway.
enabled: true,
enabled: !CI || !isPR || process.env.BROWSERSTACK_FORCE === 'true',
username: process.env.BROWSERSTACK_USERNAME,
accessKey: process.env.BROWSERSTACK_ACCESS_KEY,
build,
Expand Down
Loading