Hi everyone,

I just want to thank everyone for quick action on this. Great work.

Best regards,
Tibor


Dňa št 27. 3. 2025, 4:06 Toshiya Kobayashi <toshiyakobaya...@gmail.com>
napísal(a):

> Currently GHA is running.
>
>
> https://github.com/apache/incubator-kie-drools/actions/runs/14097858791/job/39488454368?pr=6294
>
> Probably solved by the new release
> https://www.npmjs.com/package/@kie/build-chain-action/v/3.5.9 Thanks!
>
> Jan and Marek may know some more details?
>
> On Thu, Mar 27, 2025 at 9:53 AM Alex Porcelli <porce...@apache.org> wrote:
>
> > do we have any update?
> >
> >
> > On Wed, Mar 26, 2025 at 7:13 AM Jan Šťastný <jstastn...@apache.org>
> wrote:
> >
> > > I am trying to temporarily switch the GHA to use build-chain CLI, which
> > > should be a local dev fallback (or we used it in jenkins).
> > >
> > >
> >
> https://github.com/apache/incubator-kie-kogito-pipelines/blob/try-nodejs-env-change/.ci/actions/build-chain/action.yml
> > >
> > > I am validating the change in my drools PR:
> > > https://github.com/apache/incubator-kie-drools/pull/6293
> > >
> > > Though this is not optimal, and perhaps can lead to further bumps down
> > the
> > > line.
> > >
> > > On Wed, 26 Mar 2025 at 09:52, Jan Šťastný <jstastn...@apache.org>
> wrote:
> > >
> > > > I tried the proposed workaround, doesn't seem to help.
> > > >
> > > > Though I noticed that windows PR check on Drools repo does provide at
> > > > least some stacktrace (I tried both 3.5.6 and 3.5.7):
> > > > Error: Input [Error]: Invalid flow-type
> > > >     at ActionArguments.getFlowType
> > > >
> > >
> >
> (D:\a\_actions\kiegroup\github-action-build-chain\v3.5.6\dist\index.js:51:66157)
> > > >     at ActionArguments.parse
> > > >
> > >
> >
> (D:\a\_actions\kiegroup\github-action-build-chain\v3.5.6\dist\index.js:51:66775)
> > > >     at GithubActionRunner.execute
> > > >
> > >
> >
> (D:\a\_actions\kiegroup\github-action-build-chain\v3.5.6\dist\index.js:51:59953)
> > > >     at
> > > >
> > >
> >
> D:\a\_actions\kiegroup\github-action-build-chain\v3.5.6\dist\index.js:51:664419
> > > >     at
> > > >
> > >
> >
> D:\a\_actions\kiegroup\github-action-build-chain\v3.5.6\dist\index.js:51:664430
> > > >     at Object.<anonymous>
> > > >
> > >
> >
> (D:\a\_actions\kiegroup\github-action-build-chain\v3.5.6\dist\index.js:51:664469)
> > > >     at Module._compile (node:internal/modules/cjs/loader:1529:14)
> > > >     at Module._extensions..js
> > (node:internal/modules/cjs/loader:1613:10)
> > > >     at Module.load (node:internal/modules/cjs/loader:1275:32)
> > > >     at Module._load (node:internal/modules/cjs/loader:1096:12)
> > > > Node.js v20.19.0
> > > >
> > > > I'll investigate further.
> > > >
> > > > On Wed, 26 Mar 2025 at 09:32, Gonzalo Muñoz <gonzalo51...@gmail.com>
> > > > wrote:
> > > >
> > > >> In case that it helps, I found this
> > > >>
> https://github.com/actions/runner/issues/3766#issuecomment-2753360247
> > > >>
> > > >> Regards,
> > > >> Gonzalo
> > > >>
> > > >> El mié, 26 mar 2025 a las 9:17, Jan Šťastný (<jstastn...@apache.org
> >)
> > > >> escribió:
> > > >>
> > > >>> Hello, I think this needs an input from someone well versed in
> NodeJS
> > > >>> packaging and releases.
> > > >>>
> > > >>> The most recent release of build-chain is broken I think. The
> > relevant
> > > >>> tarball does NOT contain build folder, though package.json
> references
> > > >>> that
> > > >>> in the "bin" section:
> > > >>>   "bin": {
> > > >>>     "build-chain": "./build/index.js"
> > > >>>   },
> > > >>>
> > > >>>
> > >
> >
> https://registry.npmjs.org/@kie/build-chain-action/-/build-chain-action-3.5.6.tgz
> > > >>>
> > > >>>
> > >
> >
> https://registry.npmjs.org/@kie/build-chain-action/-/build-chain-action-3.5.7.tgz
> > > >>>
> > > >>> Also GitHub runners now use NodeJS 20.19.0, not sure if build-chain
> > > built
> > > >>> for older versions should work or not (
> > > >>>
> > > >>>
> > >
> >
> https://github.com/actions/runner-images/blob/ubuntu24/20250316.1/images/ubuntu/Ubuntu2404-Readme.md
> > > >>> )
> > > >>>
> > > >>> I think the best bet now is to fix the most recent release rather
> > than
> > > >>> trying to make older versions work - as it seems plain change of
> the
> > > npm
> > > >>> version did not do the trick.
> > > >>>
> > > >>> I also noticed there's some effort on ASF infra side related to
> > > >>> allowlisting of the GHA here:
> > > >>>
> > > >>>
> > >
> >
> https://github.com/apache/infrastructure-actions/blob/main/approved_patterns.yml
> > > >>> ....
> > > >>>
> > > >>> Regards
> > > >>> Jan
> > > >>>
> > > >>> On Tue, 25 Mar 2025 at 19:27, Jan Šťastný <jstastn...@apache.org>
> > > wrote:
> > > >>>
> > > >>> > In the past we also needed to get the action allow-listed by ASF
> > > infra,
> > > >>> > not sure if it was version agnostic or not (thus the attempt to
> > > change
> > > >>> from
> > > >>> > v3 to v3.5.5 might have caused a different issue).
> > > >>> >
> > > >>> > Dne út 25. 3. 2025 19:03 uživatel Jan Šťastný <
> > jstastn...@apache.org
> > > >
> > > >>> > napsal:
> > > >>> >
> > > >>> >> Taking a quick look this looks rather like packaging, release or
> > > >>> >> installation issue.
> > > >>> >>
> > > >>> >> Dne út 25. 3. 2025 18:49 uživatel Jan Šťastný <
> > > jstastn...@apache.org>
> > > >>> >> napsal:
> > > >>> >>
> > > >>> >>> Hello, perhaps some internal GitHub API we rely on might have
> > > >>> changed.
> > > >>> >>>
> > > >>> >>> I am somewhat familiar with the tool, will take a look in the
> > > >>> morning.
> > > >>> >>>
> > > >>> >>> Regards
> > > >>> >>>
> > > >>> >>> Jan
> > > >>> >>>
> > > >>> >>> Dne út 25. 3. 2025 18:22 uživatel Toni Rikkola
> > > >>> >>> <trikk...@redhat.com.invalid> napsal:
> > > >>> >>>
> > > >>> >>>> This is a pretty critical item.
> > > >>> >>>>
> > > >>> >>>> How many guys do we know who know the setup?
> > > >>> >>>> And what is the current status?
> > > >>> >>>>
> > > >>> >>>> I have to say my knowledge on this is minimal, but this should
> > be
> > > >>> >>>> something
> > > >>> >>>> anyone from the community can maintain. Else we risk crippling
> > the
> > > >>> >>>> project
> > > >>> >>>> when we miss a key contributor.
> > > >>> >>>>
> > > >>> >>>> Toni
> > > >>> >>>>
> > > >>> >>>> On Tue, Mar 25, 2025 at 3:17 PM Tibor Zimányi <
> > > tzima...@apache.org>
> > > >>> >>>> wrote:
> > > >>> >>>>
> > > >>> >>>> > Hi everyone,
> > > >>> >>>> >
> > > >>> >>>> > the PR checks doesn't work. I am trying to take a look,
> > however
> > > it
> > > >>> >>>> would be
> > > >>> >>>> > great if someone knowledgeable in build-chain and our
> > pipelines
> > > >>> and
> > > >>> >>>> GitHub
> > > >>> >>>> > Actions takes a look, please. There are recent new versions
> of
> > > >>> >>>> build-chain
> > > >>> >>>> > releases, so I though that that is the culprit, however
> after
> > > >>> >>>> downgrade to
> > > >>> >>>> > the previous build-chain used (3.5.5), it still doesn't
> work.
> > > Any
> > > >>> >>>> idea what
> > > >>> >>>> > could be causing this is welcome. Here is an example of
> > failing
> > > PR
> > > >>> >>>> check:
> > > >>> >>>> >
> > > >>> >>>> >
> > > >>> >>>>
> > > >>>
> > >
> >
> https://github.com/apache/incubator-kie-kogito-runtimes/actions/runs/14039620267/job/39369042484
> > > >>> >>>> >
> > > >>> >>>> > Best regards,
> > > >>> >>>> > Tibor
> > > >>> >>>> >
> > > >>> >>>>
> > > >>> >>>
> > > >>>
> > > >>
> > >
> >
>

Reply via email to