[ https://issues.apache.org/jira/browse/FLINK-34961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Danny Cranmer updated FLINK-34961: ---------------------------------- Fix Version/s: jdbc-3.3.0 (was: jdbc-3.2.0) > GitHub Actions runner statistcs can be monitored per workflow name > ------------------------------------------------------------------ > > Key: FLINK-34961 > URL: https://issues.apache.org/jira/browse/FLINK-34961 > Project: Flink > Issue Type: Improvement > Components: Build System / CI > Reporter: Matthias Pohl > Priority: Major > Labels: pull-request-available, starter > Fix For: kafka-4.0.0, jdbc-3.1.3, kafka-3.2.0, jdbc-3.3.0 > > > Apache Infra allows the monitoring of runner usage per workflow (see [report > for > Flink|https://infra-reports.apache.org/#ghactions&project=flink&hours=168&limit=10]; > only accessible with Apache committer rights). They accumulate the data by > workflow name. The Flink space has multiple repositories that use the generic > workflow name {{CI}}). That makes the differentiation in the report harder. > This Jira issue is about identifying all Flink-related projects with a CI > workflow (Kubernetes operator and the JDBC connector were identified, for > instance) and adding a more distinct name. -- This message was sent by Atlassian Jira (v8.20.10#820010)