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