Set incompatible_strict_action_env and announce_rc in CI

Author: hofbi

.bazelci/presubmit.yml

@@ -34,6 +34,7 @@ buildifier:
   build_flags:
     - "--keep_going"
     - "--build_tag_filters=-integration-test"
+    - "--announce_rc"
   test_targets:
     - "--"
     - "..."
@@ -160,6 +161,7 @@ tasks:
       - "--enable_workspace"
       - "--keep_going"
       - "--build_tag_filters=-integration-test"
+      - "--action_env=PATH"
     test_targets:
       - "--"
       - "..."
@@ -180,6 +182,8 @@ tasks:
     <<: *reusable_config
     name: "Default: Windows"
     platform: windows
+    build_flags:
+      - "--action_env=PATH"
     test_flags:
       - "--test_tag_filters=-integration-test,-fix-windows"
   rbe_min:

.bazelrc

@@ -20,6 +20,8 @@ build --incompatible_default_to_explicit_init_py
 # Ensure ongoing compatibility with this flag.
 common --incompatible_disallow_struct_provider_syntax
 
+common --incompatible_strict_action_env
+
 # Windows makes use of runfiles for some rules
 build --enable_runfiles
 

examples/bzlmod/.bazelrc

@@ -7,4 +7,5 @@ test --test_output=errors --enable_runfiles
 
 # Windows requires these for multi-python support:
 build --enable_runfiles
+build --incompatible_strict_action_env
 common:bazel7.x --incompatible_python_disallow_native_rules

tests/integration/custom_commands_test.py

@@ -12,7 +12,6 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
-import logging
 import unittest
 
 from tests.integration import runner