Integrate the released fortune-teller package

Note:
1. The official release pipeline is not yet setup. This package is
   published by local testing of fortune-teller release
2. We can see the package in the output
   bazel-workstation/external/workstation_external_packages, but this
   package is not yet added to the product. Still waiting for product
   assembly support

Change-Id: I84a4b2c3ab6f1649f90617b8baca1d3c8c800fbd
Reviewed-on: https://fuchsia-review.googlesource.com/c/workstation/+/669283
Reviewed-by: Renato Mangini Dias <mangini@google.com>
Commit-Queue: Jiaming Li <lijiaming@google.com>
2 files changed
tree: 32511f7647c84ac13cf47a63bb06235586125206
  1. hooks/
  2. scripts/
  3. src/
  4. third_party/
  5. tools/
  6. vendor/
  7. .bazelrc
  8. .bazelversion
  9. .gitignore
  10. .gitmodules
  11. .manifest
  12. artifact_lock.json
  13. artifact_spec.json
  14. AUTHORS
  15. BUILD.bazel
  16. checksum.json
  17. cipd.ensure
  18. cipd_lock.versions
  19. CONTRIBUTING.md
  20. LICENSE
  21. OWNERS
  22. PATENTS
  23. README.md
  24. WORKSPACE.bazel
README.md

Workstation.git

The workstation.git repository holds the source code for building the Workstation outside of fuchsia.git. For more information, see RFC-0095.

This repository is a work in progress and should be considered experimental- the official Workstation product is still in the main fuchsia.git repository.

Fetch submodules

This project uses git submodules. After checking out a branch run the git submodule command to update the dependencies.

git submodule update --init --recursive

Bootstrap

Bootstrap script in scripts/bootstrap.sh will fetch bazel.

The Workstation repository uses Bazel for its build system. To ensure that you are using the version of Bazel that was tested in CQ/CI we recommend using bazelisk. You can either add bazelisk to your path or invoke it directly.

# Assumes that WORKSTATION_REPO is set to your checkout directory
export PATH="${WORKSTATION_REPO}/tools:$PATH"

Build instructions

Pave using

bazel run //src/product:workstation_x64_paver

Additional arguments may be supplied following a -- token, matching the arguments given to the bootserver tool.

Other targets can be found at src/build/BUILD.bazel

Generated files

artifact_spec.json is generated by

bazel run //tools/build_generator

See tools/build_generator/build_generator.go for more information. Eventually, this file will be maintained by hand.

artifact_lock.json is generated by the command:

bazel run artifact_lock_updater

This is an input to the fuchsia_product_repository WORKSPACE target.

checksum.json is generated by the command

bazel run @workstation_external_packages//:workspace_checksum_updater

and is also an input to the fuchsia_product_repository WORKSPACE target.

There are more generated files in src/product. See src/product/README.md for information.