Hi Lorenzo,
There is a umbrella ticket [1] but it is intended to track the CI
feature implementation and is now closed.
I think the best is that each connector maintainer does his own ticket.
Here is the one I did for Cassandra (there is an ongoing PR also): [2]
Best
Etienne
[1] https://issues.apache.org/jira/browse/FLINK-34136
[2] https://issues.apache.org/jira/browse/FLINK-32353
Le 04/03/2024 à 11:40, lorenzo.affe...@ververica.com a écrit :
Thank you Etienne for the information.
Is there any Jira ticket about this?
Also an umbrella one?
Or connector maintainers will do on their own?
Thank you!
On Mar 4, 2024 at 10:23 +0100, Etienne Chauchot
<echauc...@apache.org>, wrote:
Hi connector authors,
I'd like to bring a piece of information about the CI of connectors:
With the release of flink-connector-parent 1.1.0, you can now skip the
archunit tests for a particular CI build as described here [1].
Indeed, each connector needs to be tested against last 2 minor versions
of Flink but there is a single archunit rules violation store.
Sometimes, the rules change between these 2 Flink versions and you need
to freeze the violations store to tackle the violations later on. This
change is useful to freeze the violation store and execute the archunit
tests for the Flink version the connector was built against [2] but
disable the archunit tests with the other Flink version [1].
Best
Etienne
[1]
https://github.com/apache/flink-connector-shared-utils/blob/b5ad097df25973ad05d0d6af0f988b65b0d8cd22/.github/workflows/_testing.yml#L39
[2]
https://github.com/apache/flink-connector-shared-utils/blob/b5ad097df25973ad05d0d6af0f988b65b0d8cd22/.github/workflows/_testing.yml#L46
