[roll] Roll fuchsia [bazel] re-org bazel logs per fx-build/invocation

Organize bazel logs per fx-build, per invocation.

log structure:
out/_build_logs/OUTDIR_BASENAME/build.$date.XXXXXXXX/bazel_logs/invocation-$date--$id

wrapper.bazel.sh: dynamically set per-invocation log dir under
$FX_BUILD_LOGDIR as per above log structure.
Removed log-rotation, now that we capture everything.

workspace_utils.py: no longer place logs_dir under top_dir.

template.bazelrc: moved log flags to wrapper.bazel.sh

template.bazel.sh.config: removed log dir, now dynamic in
wrapper.bazel.sh.

'fx report-last-build' automatically includes everything under
the per-fx-build _build_logs dir.

bazel->ResultStore should still upload the relocated logs as invocation
artifacts using their basename (unchanged).

Original-Fixed: 490517609
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1531621
Original-Revision: d382d155eff1fb160e84cea3a930b44bb07f02bb
GitOrigin-RevId: ffbf39313a556330c500b21a52140ba4650f66ee
Change-Id: I9f83af45a69d110859508920d9baabc2840c583a
1 file changed
tree: bd4ba2b8f472d0cc9025f0fe725590d351de65ca
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cobalt
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.