Rainer Gerhards 90131e971e ci: keep daily Kafka configure fresh
Why: Daily focused runs are intended to exercise the current tree and current runner environment without stale cross-run configure state.

Impact: The daily Kafka lane no longer reuses config.cache, setup failures do not trigger secondary coverage failures, and the tracking issue identifies failed lanes.

Before/After: Before, a restored Kafka config.cache could reject new coverage flags and obscure the root cause with coverage cleanup failures. After, Kafka configures fresh and failure reports name the failed lane and artifact.

Technical Overview: Removed the actions/cache step for the daily Kafka configure cache.

Technical Overview: Removed --cache-file=config.cache from the Kafka configure command.

Technical Overview: Added an id to the prepare step and run coverage/Codecov only after configure succeeds.

Technical Overview: Extended the report job to read workflow jobs and include failed daily lanes plus expected ci-failure artifact names in the tracking issue.

Technical Overview: Added actions:read permission for the report job so it can inspect run jobs.

Issue: https://github.com/rsyslog/rsyslog/issues/7156

With the help of AI-Agents: Codex
2026-06-02 09:47:10 +02:00
..
2026-05-13 09:33:38 +02:00