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

Add build_omaha option to create_dist command #1800

Merged
merged 1 commit into from
Oct 29, 2018

Conversation

simonhong
Copy link
Member

@simonhong simonhong commented Oct 23, 2018

Build omaha stub/standalone installer when --build_omaha option is
passed to create_dist command. Also, tag_ap should be passed for tagging.

This new bulid_omaha option will create five additional executables in out/Release/
Also, we can see UAC prompt at the start of omaha build because omaha can be built with admin mode.

For example, when we run yarn create_dist Release --build_omaha --channel=beta --tag_ap=x64-be , it will create five more executables in out/Release (in this case 70.0.58.1) like below.

  • silent installer: brave_installer_70_0.58_1.exe
  • stub installer:
    • BraveBrowserBetaSetup_70_0_58_1.exe
    • DebugBraveBrowserBetaSetup_70_0_58_1.exe
  • standalone installer:
    • BraveBrowserStandaloneBetaSetup_70_0_58_1.exe
    • DebugBraveBrowserStandaloneBetaSetup_70_0_58_1.exe

Before trying to build omaha with this new option, please try to build omaha in vendor/omaha first.
Omaha needs more additional build environment setup.

This new option doesn't affect existing behavior.

Close #1784
Issue Issue: #688

Submitter Checklist:

  • Submitted a ticket for my issue if one did not already exist.
  • Used Github auto-closing keywords in the commit message.
  • Added/updated tests for this change (for new code or code which already has tests).
  • Verified that these changes build without errors on
    • Windows
    • macOS
    • Linux
  • Verified that these changes pass automated tests (npm test brave_unit_tests && npm test brave_browser_tests) on
    • Windows
    • macOS
    • Linux
  • Ran git rebase master (if needed).
  • Ran git rebase -i to squash commits (if needed).
  • Tagged reviewers and labelled the pull request as needed.
  • Requested a security/privacy review as needed.

Test Plan:

Reviewer Checklist:

  • New files have MPL-2.0 license header.
  • Request a security/privacy review as needed.
  • Adequate test coverage exists to prevent regressions.

@bsclifton
Copy link
Member

@simonhong when this is ready for review, it would be great to understand what arguments get passed in for tagging? 😄

@simonhong
Copy link
Member Author

@bsclifton Oh,, I didn't consider tagging process for this sub-command :) This sub-command should receive tagging infos together.

@bsclifton
Copy link
Member

@simonhong not sure I follow - how does it know what the product guid / channel are? Those are required for creating the stub installer, right?

@simonhong
Copy link
Member Author

simonhong commented Oct 24, 2018

@simonhong simonhong force-pushed the build_omaha_sub_command_in_create_dist branch from 52ac366 to 2d28de9 Compare October 25, 2018 02:43
Build omaha stub/standalone installer when --build_omaha option is
passed to create_dist command. Also, tag_ap should be passed for
tagging.
@simonhong simonhong force-pushed the build_omaha_sub_command_in_create_dist branch from 2d28de9 to 3364408 Compare October 25, 2018 07:42
@simonhong simonhong changed the title WIP: Add build_omaha sub command to create_dist command WIP: Add build_omaha option to create_dist command Oct 26, 2018
@@ -82,6 +84,7 @@ Config.prototype.buildArgs = function () {
brave_version_minor: version_parts[1],
brave_version_build: version_parts[2],
chrome_version_string: this.chromeVersion,
chrome_version_major: chrome_version_parts[0],
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

During the installer build, different style of brave full version is used like 70.0.58.1 or 70_0_58_1.
To make these strings easily in gn, pass chromium's major version number.

@simonhong simonhong changed the title WIP: Add build_omaha option to create_dist command Add build_omaha option to create_dist command Oct 26, 2018
Copy link
Contributor

@emerick emerick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@emerick emerick merged commit 5dd2b03 into master Oct 29, 2018
@emerick emerick deleted the build_omaha_sub_command_in_create_dist branch October 29, 2018 18:26
emerick added a commit that referenced this pull request Oct 29, 2018
…_dist

Add build_omaha option to create_dist command
emerick added a commit that referenced this pull request Oct 29, 2018
…_dist

Add build_omaha option to create_dist command
@emerick
Copy link
Contributor

emerick commented Oct 29, 2018

master: 5dd2b03
0.56.x: 6707107
0.57.x: ff92a75

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants