Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
slapos slapos
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Labels
    • Labels
  • Merge requests 122
    • Merge requests 122
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedi
  • slaposslapos
  • Merge requests
  • !138

Merged
Created Feb 28, 2017 by Boxiang Sun@DaetalusDeveloper

Port headless Chromium to SlapOS

  • Overview 14
  • Commits 5
  • Changes 7

This merge request port Chromium to SlapOS in headless mode.

Some notes:

  • The repo of Chromium and its dependencies are extremely big. ~19G after completely fetch. So be patient when fetch and building it...
  • Use the fetch and gclient command provided by depot_tools to fetch and synchronize source code. Do not use plain git unless you understand the chromium repo deeply. Because to the dependencies relationship of chromium is complicated. Plain git may only fetch or update part of repo[1]. Then the revisions of different dependencies are inconsistent. In this situation, you have to re-do everything from scratch. Which is time-consuming.
  • fetch command only could work in an empty dir. Use gclient to update code.
  • Each version of chromedriver(required by selenium) only support 3 major version of Chrome[2]. It often 2 version behind the latest Chromium. For example, the latest chromedriver 2.28 only support 55-57. And the latest Chromium is 59[3]. If you want to update the version. Please make sure the chromedriver could fit them.
  • The Chromium can run manually by ./chrome --headless --no-sandbox --disable-gpu. (Make sure you already use xvfb to start a display and set proper system path).
  • The [chromium-download] will fetch Chromium source code in ${buildout:parts-directory}/srcdirectory. This directory created by fetch command. Then the [chromium] section will enter this repo to fetch additional libs by gclient runhooks. So the repo will contaminant by this command. Be careful this when you need to rebuild Chromium or re-run the [chromium-download] section.

1. https://www.chromium.org/developers/how-tos/get-the-code/working-with-release-branches

2. https://sites.google.com/a/chromium.org/chromedriver/downloads

3. https://blink.lc/chromium/refs/

Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: chromium
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7