oscerd commented on issue #1862:
URL:
https://github.com/apache/camel-kamelets/issues/1862#issuecomment-5475464576
This is obsolete — YAKS no longer exists in this repository, so there are no
YAKS tests left to fail.
`19725e5d8` ("chore: Use pure Citrus instead of YAKS") removed the framework
wholesale, including the workflow that ran it:
```
.github/workflows/yaks-tests.yaml
tests/camel-kamelets-itest/src/test/resources/avro/yaks-config.yaml
tests/camel-kamelets-itest/src/test/resources/aws/ddb/yaks-config.yaml
tests/camel-kamelets-itest/src/test/resources/aws/kinesis/yaks-config.yaml
tests/camel-kamelets-itest/src/test/resources/aws/s3/yaks-config.yaml
tests/camel-kamelets-itest/src/test/resources/aws/sqs/yaks-config.yaml
... and the rest of the yaks-config.yaml files
```
Verified against current `main`:
- `find . -iname "*yaks*"` outside `.git` returns nothing
- no workflow under `.github/workflows/` references YAKS
- the only surviving mention anywhere is a historical line in `CHANGELOG.md`
Integration testing is now pure Citrus (`citrus.version` 5.0.0 in the root
pom), run by the `Integration Tests` workflow.
Closing as obsolete.
One thing worth knowing if you came here because CI looked red: the Citrus
suite **is** currently failing on `main`, but for an unrelated and much newer
reason — `mail-sink-pipe-test`, broken since #2968 changed `mail-sink` to
default to `smtps` while the Citrus mail server is plaintext. That is fixed in
#2987, along with the reason PR-level Kamelet changes were not being tested at
all (#2984).
---
_Claude Code on behalf of Andrea Cosentino_
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
