You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Pasquale Congiusti <pa...@gmail.com> on 2025/10/16 08:01:47 UTC
[ACTION NEEDED] Status of Jenkins jobs
Hi folks,
recently I've been investigating potential cleanings of our CI tasks [1].
So, I need your help to understand which are those jobs that are working,
which are under control and which ones can be removed as no longer used.
1. The core one (Camel core build and test) is running normally. However I
can see we're not having a successful build on main since long. Better
situation on 4.14 and 4.10 which is unstable due to several tests failing.
My question is: are we aware about this situation? how much is it a
problem? and, should we aim to have a green build or are there important
known issues impeding that?
2. The Camel JBang It test is unstable. I think that we should only test
the main and avoid stabilizing the CI on other branches. Last
successful build was on Oct 7th, I am not sure how stable was the situation
before. A pair of eyes on this one would be good to have.
3. Camel Quarkus snapshot deploy. Main job looks stable. Then we have 2
additional jobs on camel-main and quarkus-main that apparently are failing
since last year and always respectively. AFAICS there are dependencies
issues, so, maybe it is easy to fix. If however we cannot guarantee
stability on those branches and we don't need them, we probably better
remove these ones.
4. Camel K runtime build. This is stopped since some time already. As we're
not upgrading the project any longer (just the runtime), I'll ask for the
removal. Anybody know if this is something under our control? or, should be
ask to INFRA?
5. Camel Springboot daily JDK17. There are tests error since a month or so.
The root cause is apparently always the same: "Could not invoke deployment
method: public static org.jboss.shrinkwrap.api.Archive". If somebody can
keep an eye on this and bring it back green it would be one concern less to
look at. There's the very same problem on branch 4.10. Build on 4.14 is not
working as it seems some broken dependency. I think these ones should be
easy to fix.
6. Camel Springboot daility ppc64le. Same problem as in point 5. Fixing
there will clear this as well.
Thanks in advance for the support.
Regards,
Pasquale.
[1] https://ci-builds.apache.org/job/Camel/
Re: [ACTION NEEDED] Status of Jenkins jobs
Posted by Pasquale Congiusti <pa...@gmail.com>.
I've also identified the following pipelines as empty (missing Jenkinsfile):
Camel Release Dryrun
<https://ci-builds.apache.org/job/Camel/job/Camel%20Release%20Dryrun/>
Camel Full Pipeline Weekly
<https://ci-builds.apache.org/job/Camel/job/Camel%20Full%20Pipeline%20Weekly/>
I understand we can delete them as well. Any objection?
Pasquale.
On Thu, Oct 16, 2025 at 2:21 PM James Netherton <ja...@gmail.com>
wrote:
> > 3. Camel Quarkus snapshot deploy.
>
> I remove build pipelines for redundant branches.
>
> --
> James
>
> On Thu, 16 Oct 2025 at 09:02, Pasquale Congiusti <
> pasquale.congiusti@gmail.com> wrote:
>
> > Hi folks,
> > recently I've been investigating potential cleanings of our CI tasks [1].
> > So, I need your help to understand which are those jobs that are working,
> > which are under control and which ones can be removed as no longer used.
> >
> > 1. The core one (Camel core build and test) is running normally. However
> I
> > can see we're not having a successful build on main since long. Better
> > situation on 4.14 and 4.10 which is unstable due to several tests
> failing.
> > My question is: are we aware about this situation? how much is it a
> > problem? and, should we aim to have a green build or are there important
> > known issues impeding that?
> > 2. The Camel JBang It test is unstable. I think that we should only test
> > the main and avoid stabilizing the CI on other branches. Last
> > successful build was on Oct 7th, I am not sure how stable was the
> situation
> > before. A pair of eyes on this one would be good to have.
> > 3. Camel Quarkus snapshot deploy. Main job looks stable. Then we have 2
> > additional jobs on camel-main and quarkus-main that apparently are
> failing
> > since last year and always respectively. AFAICS there are dependencies
> > issues, so, maybe it is easy to fix. If however we cannot guarantee
> > stability on those branches and we don't need them, we probably better
> > remove these ones.
> > 4. Camel K runtime build. This is stopped since some time already. As
> we're
> > not upgrading the project any longer (just the runtime), I'll ask for the
> > removal. Anybody know if this is something under our control? or, should
> be
> > ask to INFRA?
> > 5. Camel Springboot daily JDK17. There are tests error since a month or
> so.
> > The root cause is apparently always the same: "Could not invoke
> deployment
> > method: public static org.jboss.shrinkwrap.api.Archive". If somebody can
> > keep an eye on this and bring it back green it would be one concern less
> to
> > look at. There's the very same problem on branch 4.10. Build on 4.14 is
> not
> > working as it seems some broken dependency. I think these ones should be
> > easy to fix.
> > 6. Camel Springboot daility ppc64le. Same problem as in point 5. Fixing
> > there will clear this as well.
> >
> > Thanks in advance for the support.
> >
> > Regards,
> > Pasquale.
> >
> > [1] https://ci-builds.apache.org/job/Camel/
> >
>
Re: [ACTION NEEDED] Status of Jenkins jobs
Posted by James Netherton <ja...@gmail.com>.
> 3. Camel Quarkus snapshot deploy.
I remove build pipelines for redundant branches.
--
James
On Thu, 16 Oct 2025 at 09:02, Pasquale Congiusti <
pasquale.congiusti@gmail.com> wrote:
> Hi folks,
> recently I've been investigating potential cleanings of our CI tasks [1].
> So, I need your help to understand which are those jobs that are working,
> which are under control and which ones can be removed as no longer used.
>
> 1. The core one (Camel core build and test) is running normally. However I
> can see we're not having a successful build on main since long. Better
> situation on 4.14 and 4.10 which is unstable due to several tests failing.
> My question is: are we aware about this situation? how much is it a
> problem? and, should we aim to have a green build or are there important
> known issues impeding that?
> 2. The Camel JBang It test is unstable. I think that we should only test
> the main and avoid stabilizing the CI on other branches. Last
> successful build was on Oct 7th, I am not sure how stable was the situation
> before. A pair of eyes on this one would be good to have.
> 3. Camel Quarkus snapshot deploy. Main job looks stable. Then we have 2
> additional jobs on camel-main and quarkus-main that apparently are failing
> since last year and always respectively. AFAICS there are dependencies
> issues, so, maybe it is easy to fix. If however we cannot guarantee
> stability on those branches and we don't need them, we probably better
> remove these ones.
> 4. Camel K runtime build. This is stopped since some time already. As we're
> not upgrading the project any longer (just the runtime), I'll ask for the
> removal. Anybody know if this is something under our control? or, should be
> ask to INFRA?
> 5. Camel Springboot daily JDK17. There are tests error since a month or so.
> The root cause is apparently always the same: "Could not invoke deployment
> method: public static org.jboss.shrinkwrap.api.Archive". If somebody can
> keep an eye on this and bring it back green it would be one concern less to
> look at. There's the very same problem on branch 4.10. Build on 4.14 is not
> working as it seems some broken dependency. I think these ones should be
> easy to fix.
> 6. Camel Springboot daility ppc64le. Same problem as in point 5. Fixing
> there will clear this as well.
>
> Thanks in advance for the support.
>
> Regards,
> Pasquale.
>
> [1] https://ci-builds.apache.org/job/Camel/
>
Re: [ACTION NEEDED] Status of Jenkins jobs
Posted by Claudio Miranda <cl...@claudius.com.br>.
Em qui., 16 de out. de 2025 às 09:03, Pasquale Congiusti
<pa...@gmail.com> escreveu:
>
> 5. Camel Springboot daily JDK17. There are tests error since a month or so.
> The root cause is apparently always the same: "Could not invoke deployment
I will look at the spring-boot ones.
Thanks for reporting them.
--
Claudio Miranda
claudio@claudius.com.br
Re: [ACTION NEEDED] Status of Jenkins jobs
Posted by Aurélien Pupier <ap...@redhat.com.INVALID>.
Hi,
for 1. the build is often broken effectively. From what I managed to
empirically observe, there are usually one of these reasons:
* commits pushed directly to the main branch without regenerating the code
and there is a formatting issue
* recently there was the addition of the JDK 25 to start looking at
supporting this version (and you provided a workaround for the compilation
error so we will see on next build)
* flaky tests. Some of them are known, they will require to investigate if
it is a matter of just the test or a real issue with the product (like when
a test is called "resequenceXXX and the order is not always correct):
https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20resolution%20%3D%20Unresolved%20AND%20text%20~%20%22flaky%22%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
By experience, I think the ones failing the most of them recently are
https://issues.apache.org/jira/browse/CAMEL-22525 and
https://issues.apache.org/jira/browse/CAMEL-22109
* added IT tests using containers which do not exists for s390x or ppc64le
architectures (if we can find a way to at leats check the existence of the
image in the PR would be nice but starting to check at it during PR review
woudl be a good start)
for 2. For Camel JBang IT tests, it is not a problem of instability but of
broken builds. it started to fail when there was the new 4.16.0-SNAPSHOT
created.
Caused by: org.apache.maven.project.DependencyResolutionException: Could
not resolve dependencies for project
org.apache.camel:camel-jbang-it:jar:4.16.0-SNAPSHOT
dependency: org.apache.camel:camel-test-infra-cli:jar:tests:4.16.0-SNAPSHOT
(test)
Could not find artifact
org.apache.camel:camel-test-infra-cli:jar:tests:4.16.0-SNAPSHOT
dependency:
org.apache.camel:camel-test-infra-mosquitto:jar:tests:4.16.0-SNAPSHOT (test)
Could not find artifact
org.apache.camel:camel-test-infra-mosquitto:jar:tests:4.16.0-SNAPSHOT
dependency: org.apache.camel:camel-jbang-core:jar:4.16.0-SNAPSHOT (test)
Could not find artifact
org.apache.camel:camel-jbang-core:jar:4.16.0-SNAPSHOT
I ensured that the Camel main snapshot job was successful but not
investigated more.
On Thu, Oct 16, 2025 at 10:12 AM Pasquale Congiusti <
pasquale.congiusti@gmail.com> wrote:
> Hi folks,
> recently I've been investigating potential cleanings of our CI tasks [1].
> So, I need your help to understand which are those jobs that are working,
> which are under control and which ones can be removed as no longer used.
>
> 1. The core one (Camel core build and test) is running normally. However I
> can see we're not having a successful build on main since long. Better
> situation on 4.14 and 4.10 which is unstable due to several tests failing.
> My question is: are we aware about this situation? how much is it a
> problem? and, should we aim to have a green build or are there important
> known issues impeding that?
> 2. The Camel JBang It test is unstable. I think that we should only test
> the main and avoid stabilizing the CI on other branches. Last
> successful build was on Oct 7th, I am not sure how stable was the situation
> before. A pair of eyes on this one would be good to have.
> 3. Camel Quarkus snapshot deploy. Main job looks stable. Then we have 2
> additional jobs on camel-main and quarkus-main that apparently are failing
> since last year and always respectively. AFAICS there are dependencies
> issues, so, maybe it is easy to fix. If however we cannot guarantee
> stability on those branches and we don't need them, we probably better
> remove these ones.
> 4. Camel K runtime build. This is stopped since some time already. As we're
> not upgrading the project any longer (just the runtime), I'll ask for the
> removal. Anybody know if this is something under our control? or, should be
> ask to INFRA?
> 5. Camel Springboot daily JDK17. There are tests error since a month or so.
> The root cause is apparently always the same: "Could not invoke deployment
> method: public static org.jboss.shrinkwrap.api.Archive". If somebody can
> keep an eye on this and bring it back green it would be one concern less to
> look at. There's the very same problem on branch 4.10. Build on 4.14 is not
> working as it seems some broken dependency. I think these ones should be
> easy to fix.
> 6. Camel Springboot daility ppc64le. Same problem as in point 5. Fixing
> there will clear this as well.
>
> Thanks in advance for the support.
>
> Regards,
> Pasquale.
>
> [1] https://ci-builds.apache.org/job/Camel/
>