Hello,

For the mentioned repositories this is still a way forward
- incubator-kie-drools
- incubator-kie-optaplanner
- incubator-kie-optaplanner-quickstarts
- incubator-kie-kogito-runtimes
- incubator-kie-kogito-apps
- incubator-kie-kogito-examples

For incubator-kie-kogito-images I have just verified that my "hack" allowed
us to isolate Jenkins PR checks for individual branches, but it requires
some juggling in setup-branch jobs after the branch is created:
- https://github.com/apache/incubator-kie-kogito-images/pull/1784/files

The solution to disable Jenkins PR checks in repositories above would
entail:
- removing .ci/jenkins/Jenkinsfile from each repo and branch (main + 10.0.x)
- deleting lines related to DSL generation in .ci/jenkins/dsl/jobs.groovy,
e.g.:
https://github.com/apache/incubator-kie-drools/blob/main/.ci/jenkins/dsl/jobs.groovy#L225-L226

Feel free to reach out.

Regards
Jan


On Mon, 22 Jul 2024 at 16:26, Paolo Bizzarri <pibi...@gmail.com> wrote:

> Hello everyone,
>
> we had already a vote on this topic, so ideally we should just move this
> forward.
>
> So unless we have specific motivation to review this decision, I suggest we
> move this forward by the end of the week.
>
> Regards
>
> Paolo
>
> On Fri, Jul 12, 2024 at 7:00 PM Tiago Bento <tiagobe...@apache.org> wrote:
>
> > Following up on that topic, as I see Jenkins checks are still being
> > triggered by PRs... does anyone have updates to share?
> >
> > On Thu, May 23, 2024 at 3:54 PM Jason Porter <lightguar...@apache.org>
> > wrote:
> > >
> > > I think it is worth circling back after our release to this topic,
> thank
> > you for brining it up, Chris!
> > >
> > > Also, +1 from me.
> > >
> > > On 2024/05/22 08:46:40 Christofer Dutz wrote:
> > > > +1
> > > >
> > > > Most Apache project that I’m involved in use GitHub actions for
> > testing the PRs and only use Jenkins for deploying of Snapshots and
> running
> > tests that GitHub doesn’t allow us to run.
> > > >
> > > > Chris
> > > >
> > > >
> > > > Von: Enrique Gonzalez Martinez <egonza...@apache.org>
> > > > Datum: Mittwoch, 22. Mai 2024 um 10:34
> > > > An: dev@kie.apache.org <dev@kie.apache.org>
> > > > Betreff: Re: [PROPOSAL] Abandon PR checks in Jenkins
> > > > Hi Jan,
> > > >
> > > > What is the impact for the projects ? One of my concerns is related
> to
> > > > test outcome publications. Right now github actions are a bit
> > > > cumbersome.
> > > > Can you elaborate a bit regarding the impact ?
> > > >
> > > > El mié, 22 may 2024 a las 10:00, Jan Šťastný (<jstastn...@apache.org
> >)
> > escribió:
> > > > >
> > > > > Hello,
> > > > >
> > > > > Due to our technical debt in Jenkins PR checks and repeated
> problems
> > with
> > > > > execution times and long waiting queues, I'd like to propose
> dropping
> > > > > Jenkins PR checks for repositories where we have an equivalent
> > alternative
> > > > > in GHA PR checks.
> > > > >
> > > > > That applies most probably to:
> > > > > - incubator-kie-drools
> > > > > - incubator-kie-kogito-runtimes
> > > > > - incubator-kie-kogito-apps
> > > > > - incubator-kie-kogito-examples
> > > > > - incubator-kie-optaplanner
> > > > > - incubator-kie-optaplanner-quickstarts
> > > > >
> > > > > The assumption is to do a cross-check for each repository whether
> > the scope
> > > > > of PR checks is equivalent, but generally I am positive GHA actions
> > are
> > > > > already superior in terms of flexibility and scope.
> > > > >
> > > > > What do you think?
> > > > >
> > > > > Regards
> > > > > Jan
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscr...@kie.apache.org
> > > > For additional commands, e-mail: dev-h...@kie.apache.org
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscr...@kie.apache.org
> > > For additional commands, e-mail: dev-h...@kie.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@kie.apache.org
> > For additional commands, e-mail: dev-h...@kie.apache.org
> >
> >
>

Reply via email to