Skip to content

Milestones

List view

  • Q4 Objective - Increase Bazel developer velocity

    KR: P1. Get code contributions merge in 2 business days median, monitor the velocity of Bazel developers. P1. Increase internal Bazel presubmit performance (currently 30-45 minutes, acceptable if everything is < 15min without flake) P1. Copybara is used for all our sync between Google repository and Github (right now we only have one direction, the other is handled by a legacy tool) P1. Automated service is pushing github update at every submitted change P2. 0 patch release due to regression (critical non-regression bugs are ok).

    Due by December 31, 2017
    0% complete0 open0 closed

  • Q4 Objective - Improve Bazel test coverage

    KR: - P0. Fix benchmark job (bazel side) - P0. Release: provide stable nightly and canary API - P1. Migrate all linux tests to our remote execution backend - P1. Add testing for Fedora/CentOS - P1. Add testing for various flavour of macOS - P1. Open-source more of our internal tests.

    Due by December 31, 2017
    •3/5 issues closed
    60% complete2 open3 closed

  • Q4 Objective - Lower the cost of ownership of ci.bazel.io

    KR: P0. Process: identify and train a support team for ci.bazel.io P2. Make macOS workers administrables by SSH P2. Schedule workers for regular reimaging P2. Evaluate options for turning down ci.bazel.io P2. Make bazelJob a reusable library

    Due by December 31, 2017
    •7/7 issues closed
    100% complete0 open7 closed

  • Q4 Objective - Improve automation provided by ci.bazel.io

    KR: P0. Site pipeline: Automatic push to website P1. Release: extends our release process to support other software (buildozer, buildifier, bazel-watcher) P2. Release: have our APT repository hold several versions of Bazel

    Due by December 31, 2017
    •4/5 issues closed
    80% complete1 open4 closed

  • Q4 Objective - Make Bazel CI user-friendly

    KRs: - P0. Provides a report for a test that shows where to look at - P1. Follow-up on https://issues.jenkins-ci.org/browse/JENKINS-39203 and fix the coloring of the steps - P1. Evaluate for connecting to internal google dashboard for test results (could replace the first KR.) - P1. Send mails with correct report of failures or automatically file bugs. - P1. Add remote caching - P2. Improve the VM we use for workers

    Due by December 31, 2017
    •7/7 issues closed
    100% complete0 open7 closed