You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Pasquale Congiusti (Jira)" <ji...@apache.org> on 2025/10/31 11:08:00 UTC
[jira] [Work started] (CAMEL-20875) Trigger component-test automatically on PR jobs
[ https://issues.apache.org/jira/browse/CAMEL-20875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on CAMEL-20875 started by Pasquale Congiusti.
--------------------------------------------------
> Trigger component-test automatically on PR jobs
> -----------------------------------------------
>
> Key: CAMEL-20875
> URL: https://issues.apache.org/jira/browse/CAMEL-20875
> Project: Camel
> Issue Type: Task
> Components: build system
> Reporter: Aurélien Pupier
> Assignee: Pasquale Congiusti
> Priority: Major
>
> Currently there is the possibility to trigger component test by providing a comment on a PR with /component-test.
> it would be convenient to start the test automatically.
> Maybe easier starting with Dependabot as there is the name of the updated dependency in the message.
> Not necessarily easy to kno all of the component directly impacted. Currently what I'm doing manually is:
> - pick the artifact id of modified dependency
> - do a search on language Maven pom, for instance https://github.com/search?q=repo%3Aapache%2Fcamel+huaweicloud-sdk-core+language%3A%22Maven+POM%22&type=code
> - look for components affected
> - provide the comment
> Maybe as a first iteration, providing a link in the generated comment message to the search URL can help to save few clicks
--
This message was sent by Atlassian Jira
(v8.20.10#820010)