Florian Weikert

Results 35 issues of Florian Weikert

- Expected release date: 2022-08-05 Task list: - [x] Pick release baseline: [39125bea](https://github.com/bazelbuild/bazel/commit/39125beac00d697de5e319d2b81143aa50068fa6) - [x] Create release candidate: https://releases.bazel.build/6.0.0/rolling/6.0.0-pre.20220801.1rc1/index.html - [ ] Post-submit: https://buildkite.com/bazel/bazel-bazel/builds?branch=release-6.0.0-pre.20220801.1rc1 - [ ] Push the release:...

P1
type: process
release
team-OSS

WORKSPACE: ``` workspace(name = "foo") load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive") skylib_version = "0.8.0" http_archive( name = "bazel_skylib", type = "tar.gz", url = "https://github.com/bazelbuild/bazel-skylib/releases/download/{}/bazel-skylib.{}.tar.gz".format (skylib_version, skylib_version), sha256 = "2ef429f5d7ce7111263289644d233707dba35e39696377ebab8b0bc701f7818e", ) load("@bazel_skylib//:workspace.bzl", "bazel_skylib_workspace") bazel_skylib_workspace() ```...

This commit runs `go vet` with shadowing detection (among other checks) during presubmits in order to prevent variable shadowing, which caused #185. Note: The shadowing check is no longer part...

Motivated by https://github.com/bazelbuild/bazelisk/issues/206: Our README mentions compatibility with Go 1.11, but we actually have no check in place that guarantees this statement. We should add a presubmit, given that some...

type: feature request
P2

As seen in #185 the entire --migrate workflow is untested, and thus a breakage went by unnoticed. Unfortunately #186 demonstrates that adding a test is not straightforward, and ideally we'd...

type: feature request
P2

I had to cancel https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/2193 after 13 hours (!). The culprit was [rules_nodejs (rbe_ubuntu1604)](https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/2193#73a307c3-5c1e-43c0-a737-c2a0cd6ed940): The first task timed out after 8 hours, the second one had been running for 5.5...

- Last green: https://buildkite.com/bazel/gerrit/builds/7055 at [79a017f](https://gerrit.googlesource.com/gerrit/+/79a017f7ddb80047232a04a24c83ae37812a3e47) - First red: https://buildkite.com/bazel/gerrit/builds/7056 at [caa7997](https://gerrit.googlesource.com/gerrit/+/caa7997c551462e210054265af4843f7a5816c51) Based on the [log](https://gerrit.googlesource.com/gerrit/+log?s=08325a350ffc6c3264535819456c9f0765fe3229) [2b5fe09](https://gerrit.googlesource.com/gerrit/+/2b5fe095f9431e995b23d3517a052fa7f4c36638) looks like the potential culprit.

Currently there is no policy regulating which projects are accepted on Bazel CI. Users simply file an issue, and we periodically work through the backlog. Going forward this has to...

Currently the [issue template](https://github.com/bazelbuild/continuous-integration/blob/master/.github/ISSUE_TEMPLATE/adding-your-project-to-bazel-ci.md) only asks for the existence of a presubmit configuration. However, there are actually more steps for onboarding a project that depend on the project maintainer: 1....