[
https://issues.apache.org/jira/browse/CAMEL-21647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17922719#comment-17922719
]
Marco Carletti commented on CAMEL-21647:
----------------------------------------
with the following pull requests, we can now use the current snapshot (at least
the latest snapshots on the repositories) and set the versions of both Camel
JBang and Camel separately
* [Pull #16968|https://github.com/apache/camel/pull/16968]
* [Pull #16936|https://github.com/apache/camel/pull/16936]
* [Pull #17009|https://github.com/apache/camel/pull/17009]
The _cli.jbang.version_ property will set the value of the Camel JBang version
and the _cli.service.execute.version_ will set the value of the Camel version
to execute.
By default the _cli.jbang.version_ uses the version of the maven project, so in
the main branch it is the current snapshot, and the
_cli.service.execute.version_ is the default one in that Camel JBang version
(eg currently both are 4.10.0-SNAPSHOT in the main branch)
> Create a jenkins job for Camel JBang IT test suite
> --------------------------------------------------
>
> Key: CAMEL-21647
> URL: https://issues.apache.org/jira/browse/CAMEL-21647
> Project: Camel
> Issue Type: Task
> Components: build system
> Reporter: Federico Mariani
> Assignee: Andrea Cosentino
> Priority: Major
> Fix For: 4.x
>
>
> The [Camel JBang
> IT|https://github.com/apache/camel/tree/main/dsl/camel-jbang/camel-jbang-it]
> test suite is slow to execute, therefore, by default the test execution is
> disabled. Having a daily Jenkins job for the supported branches that execute
> only this test suite would be nice.
> The idea is the following:
> * main - tests the latest SNAPSHOT
> * 4.x branches, test the latest released 4.x camel jbang version (not the
> SNAPSHOT), ex. camel-4.8.x will be tested via camel jbang 4.8.3 (latest 4.8.x
> camel jbang release at this time)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
