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

Enhancements to the Build Bisect tool #3746

Closed
13 tasks
bsclifton opened this issue Mar 15, 2019 · 1 comment
Closed
13 tasks

Enhancements to the Build Bisect tool #3746

bsclifton opened this issue Mar 15, 2019 · 1 comment
Assignees
Labels
closed/stale Issue is no longer relevant, perhaps because the feature it refers to has been deprecated. dev-experience dev-setup

Comments

@bsclifton
Copy link
Member

bsclifton commented Mar 15, 2019

Description

The build bisect tool was introduced with brave/brave-core#1833

Feature requests

  • Get this working on Windows
  • Get this working on Linux
  • Offer a way to pre-download all (or some) of the releases
  • Offer a way to cache the releases? (perhaps it can check SHA in GitHub against local disk, for example)
  • For use-cases like rewards, consider using staging environment by default (to prevent creating lots of wallets)
  • Tie the findings of the tool into an issue
    • potentially create an issue; prompt user for title/desc and then include the identified release / commits
    • if issue already exists, add a comment after tool is ran to provide the release / commits where problem was identified
  • Be able to pass Chromium feature flags in!
  • New non-interactive mode flag: Spit out all versions, organized by release channels (ex: --show-versions)
  • Be able to use a LOCAL profile also, instead of specifying a ZIP
  • Consider tying this into the Chromium bisect tool (for finding bugs in Chromium)

Refactoring notes

Areas where the code could be cleaner

  • token is used, but is honestly not needed
  • use util methods where possible
  • create an npm command for this!
@bsclifton
Copy link
Member Author

Closing as stale. Tool worked on macOS - may need adjustments if we pick back up. But not used AFAIK.

@bsclifton bsclifton added the closed/stale Issue is no longer relevant, perhaps because the feature it refers to has been deprecated. label Jul 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed/stale Issue is no longer relevant, perhaps because the feature it refers to has been deprecated. dev-experience dev-setup
Projects
None yet
Development

No branches or pull requests

1 participant