keycloak/26.0.0 package update

[octo-sts]

[octo-sts]

Open AI suggestions to solve the build error:

The error log indicates that there is a non-readable POM file at the path `/home/build/adapters/oidc/js/pom.xml`, with the specific error being "No such file or directory." 

To resolve this issue, you should:

1. Verify that the file path `/home/build/adapters/oidc/js/pom.xml` is correct.
2. Check if the `pom.xml` file actually exists at the specified location.
3. If the file is located elsewhere, update the path in your build configuration to point to the correct location.
4. After making any necessary corrections, attempt to rebuild the project.

[debasishbsws]

keycloak/keycloak#32824 related upstream issue

[debasishbsws]

The build will still fail until the bitnami container release keycloke 26. it is still in 25 https://github.com/bitnami/containers/tree/main/bitnami/keycloak

[octo-sts]

Open AI suggestions to solve the build error:

The error log indicates a failure in executing the goal `com.github.eirslett:frontend-maven-plugin:1.15.0:pnpm` during the `pnpm-build` phase on the `keycloak-admin-ui` project. The task `pnpm build` failed with an exit value of 1. Here are some steps to troubleshoot:

1. Check the `pnpm` build logs for specific error messages.
2. Run `pnpm install` to ensure all dependencies are correctly installed.
3. Verify that the `pnpm` version is compatible with your project requirements.
4. Inspect the `package.json` file for any issues in the build scripts.
5. Try running `pnpm build` manually to identify and debug the problem.

[octo-sts]

Open AI suggestions to solve the build error:

The error message indicates a failure in executing the `pnpm build` task within the `keycloak-admin-ui` project. The process exited with an error code 1. To resolve this issue, you can:

1. Check the `pnpm` build logs for specific errors.
2. Ensure all dependencies are correctly installed.
3. Verify that the `pnpm` version is compatible with your project.
4. Run `pnpm install` to update dependencies.
5. Clear the `node_modules` directory and `pnpm-lock.yaml` file, then attempt to rebuild.
6. Review the `package.json` file for any scripts that might be causing the failure.

[debasishbsws]

The package build is failing because the bitnami container did not release for keycloke 26. it is still in 25 https://github.com/bitnami/containers/tree/main/bitnami/keycloak

But the error we are encountering is different for x86 and aarch64.
When I locally try to build locally with the old bitnami 25 configuration the x86_64 build is passing but it is not working for aarch_64.

The clear distinction we can make here by looking at the log difference, x86 is failing in the subpackage pipeline but in aarch64 it is failing in the main package pipeline

[mamccorm]

Hey @debasishbsws. I don't expect this will be all the changes necessary for Keycloak v26 (which is a significant update and a LOT of changes), but fixed up a couple of things in this commit: 09deaab

[octo-sts]

Open AI suggestions to solve the build error:

The error log indicates a failure in executing the goal `com.github.eirslett:frontend-maven-plugin:1.15.0:pnpm` during the `pnpm-build` phase on the `keycloak-admin-ui` project. The task `'pnpm build'` failed with an exit value of 1. Here are some steps to troubleshoot:

1. Check the `pnpm` logs for detailed error messages.
2. Verify the dependencies listed in `package.json` for any issues.
3. Ensure that the `pnpm` version is compatible with your project requirements.
4. Run `pnpm install` to update and install all dependencies.
5. Check the build scripts for any syntax errors or misconfigurations.
6. Retry running `pnpm build` after addressing any identified issues.

[octo-sts]

Open AI suggestions to solve the build error:

The error log indicates a failure in executing the goal `com.github.eirslett:frontend-maven-plugin:1.15.0:pnpm` during the `pnpm-build` phase of the `keycloak-admin-ui` project. The specific error is that the task `'pnpm build'` failed with an exit value of 1. Here are some steps to address the issue:

1. Check the `pnpm` build logs for specific errors.
2. Ensure all dependencies are correctly installed.
3. Verify the `pnpm` version compatibility with the project.
4. Run `pnpm install` to update dependencies.
5. Check for any missing or misconfigured scripts in `package.json`.
6. Re-run the build command.

[octo-sts]

Open AI suggestions to solve the build error:

The error log indicates a failure in executing the goal `com.github.eirslett:frontend-maven-plugin:1.15.0:pnpm` during the `pnpm-build` phase on the `keycloak-admin-ui` project. The task `'pnpm build'` failed with an exit value of 1. Here are some steps to troubleshoot:

1. Check the `pnpm` logs for more detailed error messages.
2. Ensure that all dependencies listed in `package.json` are correct and up-to-date.
3. Verify that the version of `pnpm` being used is compatible with your project.
4. Run `pnpm install` to update and install all necessary dependencies.
5. Look for any syntax errors or issues in your build scripts that might be causing the failure.

[cpanato]

it is failing in arm in the part

 Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.15.0:pnpm (pnpm-build) on project keycloak-admin-ui: Failed to run task: 'pnpm build' failed. org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1) -> [Help 1]

[debasishbsws]

Guessing but it might be related to the same issue @kranurag7 is talking about in trino package-update PR
Anurag comment

given upstream is using frontend-maven-plugin to download node and npm, it won't work on aarch64 architecture because the plugin doesn't support aarch64 architecture.
It'll download node for x86 on arch which is incompatible. We need to use local nodejs and npm and from my previous work on hadoop, the local nodejs use is not officially allowed by the plugin. Somehow exec plugin needs to be tweaked to hack into node and allow local node usage.
upstream issues about the same: eirslett/frontend-maven-plugin#884 and eirslett/frontend-maven-plugin#1154

[octo-sts]

Gen AI suggestions to solve the build error:

The error message indicates a failure in executing the `pnpm build` task within the `keycloak-admin-ui` project, specifically through the `frontend-maven-plugin`. The process exited with an error code 1. Here are some suggestions to address the issue:

1. Check the `pnpm` logs for more detailed error information.
2. Ensure that the dependencies listed in `package.json` are correct and up-to-date.
3. Verify that the version of `pnpm` being used is compatible with your project.
4. Run `pnpm install` to update and install all necessary dependencies.
5. Look for any syntax errors in your build scripts that might be causing the failure.
6. After addressing any issues, try running `pnpm build` again.

[cpanato]

Guessing but it might be related to the same issue @kranurag7 is talking about in trino package-update PR Anurag comment

given upstream is using frontend-maven-plugin to download node and npm, it won't work on aarch64 architecture because the plugin doesn't support aarch64 architecture.
It'll download node for x86 on arch which is incompatible. We need to use local nodejs and npm and from my previous work on hadoop, the local nodejs use is not officially allowed by the plugin. Somehow exec plugin needs to be tweaked to hack into node and allow local node usage.
upstream issues about the same: eirslett/frontend-maven-plugin#884 and eirslett/frontend-maven-plugin#1154

that makes sense, what we should do here?

cc @TaylorBloom129 @mamccorm @xnox

[debasishbsws]

It seems like for the hadoop-3.3 package we are skiping the UI build for aarch64

  - if: ${{build.arch}} == "aarch64"
    runs: |
      mvn -Pdist,native,src -DskipTests -Denforcer.skip=true -Dtar -Dmaven.javadoc.skip=true -Drequire.openssl -Drequire.fuse -Drequire.snappy clean package -e -X

  - if: ${{build.arch}} == "x86_64"
    runs: |
      mvn -Pdist,yarn-ui,native,src -DskipTests -Denforcer.skip=true -Dtar -Dmaven.javadoc.skip=true -Drequire.openssl -Drequire.fuse -Drequire.snappy clean package -e -X

Not sure if that is possible here or not. or if there is another approach.

[octo-sts]

superseded by #31438