Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RHPAM-4618] update EAP XP to version 4.0.0.GA-redhat-00011 #1208

Merged
merged 1 commit into from Dec 8, 2022

Conversation

rgdoliveira
Copy link
Member

@rgdoliveira rgdoliveira commented Dec 7, 2022

This prod version is EAP XP on top of EAP 7.4.8

JIRA: https://issues.redhat.com/browse/RHPAM-4618

referenced Pull Requests:

How to replicate CI configuration locally?

Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.

build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.

How to retest this PR or trigger a specific build:
  • a pull request please add comment: Jenkins retest this

  • a full downstream build please add comment: Jenkins run fdb

  • a compile downstream build please add comment: Jenkins run cdb

  • a full production downstream build please add comment: Jenkins execute product fdb

  • an upstream build please add comment: Jenkins run upstream

This prod version is EAP XP on top of EAP 7.4.8
@rgdoliveira
Copy link
Member Author

Jenkins run fdb

@mareknovotny
Copy link
Member

Jenkins execute product fdb

Copy link
Contributor

@tomasdavidorg tomasdavidorg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I built it locally and did some testing and it looks good to me. 🙂 Thanks.

@rgdoliveira
Copy link
Member Author

Execution Summary:

[2022-12-08T12:25:45.019Z] ::group::[Full Downstream Flow] Execution Summary...
[2022-12-08T12:25:45.019Z] [INFO]  ----------------------------------------------
[2022-12-08T12:25:45.019Z] [INFO]  [kiegroup/droolsjbpm-build-bootstrap]. Execution Result: ok. Time: 10.2s (10277 ms)
[2022-12-08T12:25:45.019Z] [INFO]  [kiegroup/kie-soup]. Execution Result: ok. Time: 1m 21.3s (81308 ms)
[2022-12-08T12:25:45.019Z] [INFO]  [kiegroup/droolsjbpm-knowledge]. Execution Result: ok. Time: 27.7s (27764 ms)
[2022-12-08T12:25:45.019Z] [INFO]  [kiegroup/drools]. Execution Result: ok. Time: 21m 23.3s (1283317 ms)
[2022-12-08T12:25:45.019Z] [INFO]  [kiegroup/optaplanner]. Execution Result: ok. Time: 4m 2.4s (242423 ms)
[2022-12-08T12:25:45.019Z] [INFO]  [kiegroup/lienzo-core]. Execution Result: ok. Time: 8s (8048 ms)
[2022-12-08T12:25:45.019Z] [INFO]  [kiegroup/lienzo-tests]. Execution Result: ok. Time: 29.4s (29453 ms)
[2022-12-08T12:25:45.019Z] [INFO]  [kiegroup/appformer]. Execution Result: ok. Time: 15m 40.5s (940534 ms)
[2022-12-08T12:25:45.019Z] [INFO]  [kiegroup/kie-uberfire-extensions]. Execution Result: ok. Time: 4.6s (4617 ms)
[2022-12-08T12:25:45.019Z] [INFO]  [kiegroup/jbpm]. Execution Result: ok. Time: 41m 58.3s (2518309 ms)
[2022-12-08T12:25:45.019Z] [INFO]  [kiegroup/droolsjbpm-integration]. Execution Result: ok. Time: 28m 9.1s (1689155 ms)
[2022-12-08T12:25:45.019Z] [INFO]  [kiegroup/kie-wb-playground]. Execution Result: ok. Time: 12.9s (12993 ms)
[2022-12-08T12:25:45.019Z] [INFO]  [kiegroup/kie-wb-common]. Execution Result: ok. Time: 28m 12.9s (1692944 ms)
[2022-12-08T12:25:45.019Z] [INFO]  [kiegroup/drools-wb]. Execution Result: ok. Time: 19m 43.5s (1183561 ms)
[2022-12-08T12:25:45.019Z] [INFO]  [kiegroup/jbpm-work-items]. Execution Result: ok. Time: 10m 45.6s (645609 ms)
[2022-12-08T12:25:45.019Z] [INFO]  [kiegroup/jbpm-wb]. Execution Result: ok. Time: 11m 10.4s (670438 ms)
[2022-12-08T12:25:45.019Z] [INFO]  [kiegroup/optaplanner-wb]. Execution Result: error. Time: 1m 21.1s (81162 ms)
[2022-12-08T12:25:45.019Z] [INFO]  ----------------------------------------------

FDPB failed with non related error to kie-wb-distributions

[2022-12-08T12:25:12.999Z] [INFO] Compiling module org.optaplanner.workbench.OptaPlannerWorkbench
[2022-12-08T12:25:45.019Z] [INFO]    Tracing compile failure path for type 'org.kie.workbench.common.screens.library.client.screens.project.ProjectMetricsScreen'
[2022-12-08T12:25:45.019Z] [INFO]       [ERROR] Errors in 'jar:file:/home/jenkins/.m2/repository/org/kie/workbench/screens/kie-wb-common-library-client/7.74.0-SNAPSHOT/kie-wb-common-library-client-7.74.0-SNAPSHOT-sources.jar!/org/kie/workbench/common/screens/library/client/screens/project/ProjectMetricsScreen.java'
[2022-12-08T12:25:45.019Z] [INFO]          [ERROR] Line 77: No source code is available for type org.kie.workbench.common.screens.contributors.service.ContributorsService; did you forget to inherit a required module?
[2022-12-08T12:25:45.019Z] [INFO]    Tracing compile failure path for type 'org.kie.workbench.common.screens.library.client.screens.OrgUnitsMetricsScreen'
[2022-12-08T12:25:45.019Z] [INFO]       [ERROR] Errors in 'jar:file:/home/jenkins/.m2/repository/org/kie/workbench/screens/kie-wb-common-library-client/7.74.0-SNAPSHOT/kie-wb-common-library-client-7.74.0-SNAPSHOT-sources.jar!/org/kie/workbench/common/screens/library/client/screens/OrgUnitsMetricsScreen.java'
[2022-12-08T12:25:45.019Z] [INFO]          [ERROR] Line 100: No source code is available for type org.kie.workbench.common.screens.contributors.service.ContributorsService; did you forget to inherit a required module?

@rgdoliveira rgdoliveira merged commit bdb21f8 into kiegroup:main Dec 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants