Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add e2e traits test for cron #5414

Merged
merged 1 commit into from
Apr 25, 2024
Merged

Add e2e traits test for cron #5414

merged 1 commit into from
Apr 25, 2024

Conversation

tdiesler
Copy link
Contributor

No description provided.

Copy link
Contributor

@squakez squakez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the cron trait scenarios are implicitly tested in https://github.com/apache/camel-k/blob/main/e2e/common/misc/cron_test.go so this would be a duplicate - you can see cron has the auto setting as default, which mean, it scans the source to discover if any cron trait configuration can be inferred by the source.

@squakez
Copy link
Contributor

squakez commented Apr 24, 2024

BTW, as mentioned already in the past, please, avoid referencing any downstream reference such as specific company Jira issues or the like. Thanks.

@tdiesler tdiesler changed the title [CMLK-1387] Add e2e traits test for cron Add e2e traits test for cron Apr 24, 2024
@tdiesler
Copy link
Contributor Author

tdiesler commented Apr 24, 2024

The test verifies that -t cron.schedule actually overrides the schedule in the yaml

@tdiesler
Copy link
Contributor Author

Ready to merge

@squakez squakez merged commit a965bce into apache:main Apr 25, 2024
13 checks passed
@squakez
Copy link
Contributor

squakez commented Apr 25, 2024

Please, backport to release-2.3.x

@tdiesler tdiesler deleted the CMLK-1387-cron branch April 25, 2024 08:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants