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
AF-2933 : Business Cental fails to start with error "no marshaller for type: org.guvnor.structure.contributors.Contributor" after migrating to 7.12.0 #1237
Conversation
Jenkins run fdb |
Jenkins run fdb |
@akumar074 Thanks for the PR! PR has fixed the Marshaling error and spaces/projects are successfully migrated to the new version(7.12.0) of BC using migration tool. But I have observed below repository not found error with dashbuilder while starting business central with the migrated version.
2.Can you please add relevant tests for this issue? Please let me know your inputs. Thanks, |
return objectStorage.read(path); | ||
} | ||
} catch (Exception e) { | ||
throw new RuntimeException(e); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer to pass message while creating the runtime exception
logger.error(e.getMessage()); | ||
return fixContributorClassInSpaceInfo(); | ||
} | ||
throw new RuntimeException(e); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer to pass an exception message string while creating the runtime exception
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1, also we are not loggin the problem unless it is a MarshallingException problem.
Jenkins run fdb |
1 similar comment
Jenkins run fdb |
@akumar074 |
Hi @sthundat |
Jenkins run fdb |
Jenkins run fdb |
1 similar comment
Jenkins run fdb |
Jenkins run cdb |
Jenkins run fdb |
…or type: org.guvnor.structure.contributors.Contributor" after migrating to 7.12.0 - Fixing Contributor and ContributorType packages
Jenkins run fdb |
1 similar comment
Jenkins run fdb |
…or type: org.guvnor.structure.contributors.Contributor" after migrating to 7.12.0 - Fixing Contributor and ContributorType packages
Jenkins run fdb |
Hi @sthundat @adrielparedes @RishiRajAnand I have made changes according to the comments. Please rereview the PR when you can. |
Jenkins run fdb |
SonarCloud Quality Gate failed. |
Hi @akumar074 , |
@sthundat I will build the migration tool locally and share the zip with you |
Add-ons Zip for migration tool: https://drive.google.com/file/d/1DJpna3Tzw9u1ZWLWfz4hPkuS5_CNSr0e/view?usp=sharing |
Jenkins run fdb |
Jenkins run cdb |
@akumar074 |
Hi @adrielparedes , We have all the approvals required with Green FDB build. Can we go ahead and merge this? |
Jenkins run cdb |
JIRA:
AF-2933
RHPAM-4152
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