[
https://issues.apache.org/jira/browse/FLINK-31923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733002#comment-17733002
]
Martijn Visser commented on FLINK-31923:
----------------------------------------
Fixed in:
apache/flink-connector-gcp-pubsub@main: 01e1b6fa0d830aea734201f63c1ee58874d5fa23
apache/flink-connector-rabbitmq@main: 6b70965d331c5f0f94bf08a7defcb7ecf62dbc5c
apache/flink-connector-jdbc@main: bd371d64be644a36b8000ed06c9afa9928cb8fc4
apache/flink-connector-pulsar@main: f463d3f707c8824bc61cce29c0efcdd4de94257e
apache/flink-connector-mongodb@main: fe65806824ae181831b3440f04cbd13bee9af95d
apache/flink-connector-opensearch@main: aa2d57ee7af212757815378ae43eec8536fcde1a
apache/flink-connector-cassandra@main: ac6cf71fb3ed73f2ca1f6414d6e22abc9c756529
apache/flink-connector-elasticsearch@main:
be0f30428fec7871644509cd431e088f1d39f390
Todo:
apache/flink-connector-aws@main:
> Connector weekly runs are only testing main branches instead of all supported
> branches
> --------------------------------------------------------------------------------------
>
> Key: FLINK-31923
> URL: https://issues.apache.org/jira/browse/FLINK-31923
> Project: Flink
> Issue Type: Bug
> Components: Build System, Connectors / Common
> Reporter: Martijn Visser
> Assignee: Martijn Visser
> Priority: Major
> Labels: pull-request-available
>
> We have a weekly scheduled build for connectors. That's only triggered for
> the {{main}} branches, because that's how the Github Actions {{schedule}}
> works, per
> https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#schedule
> We can resolve that by having the Github Action flow checkout multiple
> branches as a matrix to run these weekly tests.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
