Am doing the last minute rudimentary testing for platform 2.3.2 minor release and am reaching out for help to ensure I meet the intended requirements in this release. I have read through each ticket description,comments and also followed TALK conversation of the given ticket to understand the intended effect once the issue is fixed. I have tried testing but am confused since I can’t tell where the effect is reflected for some ticket . I therefore, humbly request you help me test or you can guide me on how to go about the tickets you reported.
@jwnasambu I don’t have any insight into TRUNK-5795, but for TRUNK-5821 I would just look at the order table in the database and confirm that indexes exist on accession_number and order_number…
@dkayiwa the release process is ongoing, only that I forgot to override the next development version parameter in openmrs-core 2.3.x while releasing which I suspect is resulting to a compilation error when I try to release on openmrs platform 2.3.x as reflected on the logs below
Thanks so so much. This is the link to openmrs-core 2.3.x CI where I forgot to override the next development version parameter and this is the CI link to openmrs Platform 2.3.x where I’m experiencing a compilation error.
@dkayiwa Kind help please! openmrs-core 2.3.x CI has build successfully after overriding the development parameter to the next version something I thought would automatically fix the build failure on openmrs platform 2.3.x and the release be reflected on the sourceforge since I had already released platform 2.3.x . On the contrary, standalone build is failing which I suspect the error source is from Liquibase. Kindly how do I go about this to finalize with this release?
I have attempt to rerun the build on platform 2.3.x branch, but am getting this error Plan 'OP-OPM7-81' started but a fatal error occurred and this is the entire error log https://pastebin.com/PczmVLKz. To figure out the cause of Unknown RepositoryDefinition 195428353) I followed this steps under "
and I didn’t see openmrs platform 2.3.x branch among the Linked repositories yet its the plan am running which makes me suspect is the cause of this error. Though I have seen the add repository option, I wouldn’t like to do it without your consent. Any help is appreciated.
I have tried to follow this guide keenly on releasing platform 2.3.x but am stack on step Number 10 and I kindly need help on the way forward. I specified the variable values as maven.release.version 2.3.2 maven.development.version 2.3.3 snapshot and build.release.type releases as its documented in the guide and can be reflected on this link but am running into a compilation error as reflected by the logs on this link https://ci.openmrs.org/browse/OP-OPM7-RTM-82/log of which I have tried to research around on the would be cause of the error and possible solution but its in vain. How can I go about this blocker?
No. I just used 2.3.2 because I had an assumption its the version which is need and the snapshot will be reflected automatically. Thanks so much for helping me identify my mistake. To fix it should I rerun the release steps again?
