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 <[email protected]> wrote: > > 3. Camel Quarkus snapshot deploy. > > I remove build pipelines for redundant branches. > > -- > James > > On Thu, 16 Oct 2025 at 09:02, Pasquale Congiusti < > [email protected]> 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/ > > >
