# OpenMRS Platform 2.3.0-beta released for testing **URL:** \ **Category:** Platform\ **Tags:** releases\ **Created:** [September 20, 2019, 1:47pm UTC](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795 "2019-09-20T13:47:19Z")\ **Posts on this page:** 20\ **Page:** 3
**Author:** ![ruhanga](https://talk.openmrs.org/user_avatar/talk.openmrs.org/ruhanga/32/8318_2.png) [@ruhanga](https://talk.openmrs.org/u/ruhanga)\ **Post date:** [October 31, 2019, 6:08pm UTC](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795/41 "2019-10-31T18:08:33Z")
Hi all, I think it’s okay taking forward the Platform 2.3.0 full release. I and @tendomart have made a number of tests with the Reference application distribution built on top of the beta version. I have tested the rest endpoints using the default demo data and I think we are good to go. A couple of more commits on the platform are probably also on their way due to the on-going work on the Data filter module. Do we want to rather give more time to include the developments for a full release? Your thought and feedback on this is very helpful. Thank you. cc: [@dev5](https://talk.openmrs.org/groups/dev5), [@dev4](https://talk.openmrs.org/groups/dev4), [@dev3](https://talk.openmrs.org/groups/dev3), [@dev2](https://talk.openmrs.org/groups/dev2)@all ---
**Author:** ![cintiadr](https://talk.openmrs.org/user_avatar/talk.openmrs.org/cintiadr/32/8081_2.png) [@cintiadr](https://talk.openmrs.org/u/cintiadr)\ **Post date:** [November 1, 2019, 9:55am UTC](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795/42 "2019-11-01T09:55:57Z")
Is there any reason why this release is not being tested in [UAT](https://ci.openmrs.org/deploy/viewDeploymentProjectEnvironments.action?id=93650946)? We have an environment only for acceptance tests for refapp releases, so if we won’t be using it anymore, I’d destroy it. ---
**Author:** ![tendomart](https://talk.openmrs.org/user_avatar/talk.openmrs.org/tendomart/32/6753_2.png) [@tendomart](https://talk.openmrs.org/u/tendomart)\ **Post date:** [November 1, 2019, 9:58am UTC](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795/43 "2019-11-01T09:58:51Z")
@cintiadr No please don’t i earlier asked but it looked like no one was using it,we still need it to optimize resources. Have you considered [these logs](https://ci.openmrs.org/deploy/viewDeploymentResult.action?deploymentResultId=167673862) ---
**Author:** ![cintiadr](https://talk.openmrs.org/user_avatar/talk.openmrs.org/cintiadr/32/8081_2.png) [@cintiadr](https://talk.openmrs.org/u/cintiadr)\ **Post date:** [November 1, 2019, 10:23am UTC](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795/44 "2019-11-01T10:23:03Z")
Can you rephrase your questions? > [@tendomart](#): > > i earlier asked but it looked like no one was using it I’m very confused what you mean by this. > [@tendomart](#): > > Have you considered [these logs](https://ci.openmrs.org/deploy/viewDeploymentResult.action?deploymentResultId=167673862) Same. ---
**Author:** ![tendomart](https://talk.openmrs.org/user_avatar/talk.openmrs.org/tendomart/32/6753_2.png) [@tendomart](https://talk.openmrs.org/u/tendomart)\ **Post date:** [November 1, 2019, 10:25am UTC](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795/45 "2019-11-01T10:25:48Z")
I have just redeployed the Refapp 2.9.0 after the broken builds and still throwing those errors.Any way to fix that ? and this [https://uat.openmrs.org/](https://uat.openmrs.org/) is unavailable ---
**Author:** ![cintiadr](https://talk.openmrs.org/user_avatar/talk.openmrs.org/cintiadr/32/8081_2.png) [@cintiadr](https://talk.openmrs.org/u/cintiadr)\ **Post date:** [November 1, 2019, 10:46am UTC](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795/46 "2019-11-01T10:46:39Z")
> [@tendomart](#): > > I have just redeployed the Refapp 2.9.0 after the broken builds and still throwing those errors.Any way to fix that ? Ok, let’s start from the beginning. Sorry, I got confused with the fact that you are releasing _platform_, and UAT-refapp is of course to be used _only_ by refapp releases, not platform. We do not have an UAT environment for platform. If you are attempting to release platform 2.3.0-beta, why would you redeployed refapp 2.9.0 to UAT-refapp? That’s very confusing. So let’s just fix builds that should exist in the first place. > [@tendomart](#): > > and this [https://uat.openmrs.org/](https://uat.openmrs.org/) is unavailable This is not a valid URL If you have questions about our environments, please refer to [docs](https://wiki.openmrs.org/display/ISM/OpenMRS+environments) ---
**Author:** ![tendomart](https://talk.openmrs.org/user_avatar/talk.openmrs.org/tendomart/32/6753_2.png) [@tendomart](https://talk.openmrs.org/u/tendomart)\ **Post date:** [November 1, 2019, 12:06pm UTC](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795/47 "2019-11-01T12:06:43Z")
Thanks , i thought there was some sort of UAT server for platform , that’s why i asked. about the error log above , the latest was showing errors run by you , am thinking it’s either 2.9.0 latest running or SNAPSHOT-2.10.0 ---
**Author:** ![mksd](https://talk.openmrs.org/user_avatar/talk.openmrs.org/mksd/32/11729_2.png) [@mksd](https://talk.openmrs.org/u/mksd)\ **Post date:** [November 1, 2019, 10:09pm UTC](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795/48 "2019-11-01T22:09:31Z")
@ruhanga as discussed within [@MekomSolutions](https://talk.openmrs.org/groups/mekomsolutions), I think we’re the only ones actively maintaining test/QA/UAT servers running Core 2.3.x. So far so good, @wyclif, thoughts? ---
**Author:** ![ruhanga](https://talk.openmrs.org/user_avatar/talk.openmrs.org/ruhanga/32/8318_2.png) [@ruhanga](https://talk.openmrs.org/u/ruhanga)\ **Post date:** [November 4, 2019, 9:35am UTC](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795/49 "2019-11-04T09:35:35Z")
Great @mksd. Thanks very much. I hope to have the full platform release by Tuesday(tomorrow) the 5th of November. Special thanks to every one that has contributed to this cause. 🙂 ---
**Author:** ![mozzy](https://talk.openmrs.org/user_avatar/talk.openmrs.org/mozzy/32/11815_2.png) [@mozzy](https://talk.openmrs.org/u/mozzy)\ **Post date:** [November 4, 2019, 9:58am UTC](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795/50 "2019-11-04T09:58:40Z")
> [@mksd](#): > > I think we’re the only ones actively maintaining test/QA/UAT servers running But is there any reason we (the community) have no single current UAT/QA test enviroment for the platform??. we seem to have alot of servers for the reff app and no single one for the platform . cc @cintiadr @dkayiwa ---
**Author:** ![cintiadr](https://talk.openmrs.org/user_avatar/talk.openmrs.org/cintiadr/32/8081_2.png) [@cintiadr](https://talk.openmrs.org/u/cintiadr)\ **Post date:** [November 4, 2019, 10:17am UTC](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795/51 "2019-11-04T10:17:29Z")
The reason is pretty simple. It wasn’t needed so far. There are no automated tests in platform that require an external qa-platform environment; so no reason to create it. The qa-refapp should be _only_ used by automated builds in refapp, which was already there. The UAT-platform wasn’t created because no one cared enough to create the environment. If there’s an actual demand and I get some help, it’s not hard. But then I need guarantees that it’s going to be updated regularly after releases (which is currently not happening with the mdsbuilder, our only platform environment - which is not a build one). ---
**Author:** ![mozzy](https://talk.openmrs.org/user_avatar/talk.openmrs.org/mozzy/32/11815_2.png) [@mozzy](https://talk.openmrs.org/u/mozzy)\ **Post date:** [November 4, 2019, 10:36am UTC](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795/52 "2019-11-04T10:36:22Z")
> [@cintiadr](#): > > mdsbuilder i was going to mention about **mdsBuilder** but you know that is strictly restricted to very few people and release managers , we shouldnt even talk about that 😀 > [@cintiadr](#): > > If there’s an actual demand and I get some help, I think the demand is there , every thing we do depends on the platform , new fixes are added every now and then . I think that is demand enough 🙂 which help is needed exactly ?? i dont think we can fail to offer the help if specified. Otherwise Good job your doing @cintiadr ---
**Author:** ![cintiadr](https://talk.openmrs.org/user_avatar/talk.openmrs.org/cintiadr/32/8081_2.png) [@cintiadr](https://talk.openmrs.org/u/cintiadr)\ **Post date:** [November 4, 2019, 10:58am UTC](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795/53 "2019-11-04T10:58:57Z")
We already have a [CI build](https://ci.openmrs.org/browse/OP-OPM) that updates [docker image openmrs-distro-platform](https://hub.docker.com/r/openmrs/openmrs-distro-platform/tags) in docker hub. It would need someone to add deployments to deploy tag ‘uat’ tag to dockerhub; exactly like it’s done to uat-refapp. From there, a new docker service needs to be created in our [docker-ansible repo](https://github.com/openmrs/openmrs-contrib-ansible-docker-compose), and that needs to have all the data needed on start up. UAT-platform will be recreated every couple of days. Only the Infra team can then deploy this application to a server, including monitoring. The last mile is updating wiki docs, creating a build to reset data in the server, change deployment to update the server, and so on. ---
**Author:** ![mozzy](https://talk.openmrs.org/user_avatar/talk.openmrs.org/mozzy/32/11815_2.png) [@mozzy](https://talk.openmrs.org/u/mozzy)\ **Post date:** [November 4, 2019, 11:16am UTC](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795/54 "2019-11-04T11:16:59Z")
Ill try do all that i can … Can we create a ticket for this to track down the work ? ---
**Author:** ![cintiadr](https://talk.openmrs.org/user_avatar/talk.openmrs.org/cintiadr/32/8081_2.png) [@cintiadr](https://talk.openmrs.org/u/cintiadr)\ **Post date:** [November 4, 2019, 11:18am UTC](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795/55 "2019-11-04T11:18:17Z")
For the build, it’s ok to change directly in CI (I can review later). For the code changes, all should require pull requests. ---
**Author:** ![mozzy](https://talk.openmrs.org/user_avatar/talk.openmrs.org/mozzy/32/11815_2.png) [@mozzy](https://talk.openmrs.org/u/mozzy)\ **Post date:** [November 4, 2019, 11:19am UTC](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795/56 "2019-11-04T11:19:19Z")
Can you create a ticket for it ? ---
**Author:** ![mksd](https://talk.openmrs.org/user_avatar/talk.openmrs.org/mksd/32/11729_2.png) [@mksd](https://talk.openmrs.org/u/mksd)\ **Post date:** [November 4, 2019, 11:50am UTC](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795/57 "2019-11-04T11:50:01Z")
We run a custom Ref App 2.10 on Core 2.3.x. It’s still early but it looks like it’s ok. Keep in mind that we are in QA stages, entering UAT. Just to say that we might consider having Ref App 2.10 run on Core 2.3.x. This should be the subject of another thread though. ---
**Author:** ![mozzy](https://talk.openmrs.org/user_avatar/talk.openmrs.org/mozzy/32/11815_2.png) [@mozzy](https://talk.openmrs.org/u/mozzy)\ **Post date:** [November 4, 2019, 11:58am UTC](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795/58 "2019-11-04T11:58:45Z")
> [@mksd](#): > > Ref App 2.10 run on Core 2.3. 😃 That sounds intresting. ---
**Author:** ![mogoodrich](https://talk.openmrs.org/user_avatar/talk.openmrs.org/mogoodrich/32/3324_2.png) [@mogoodrich](https://talk.openmrs.org/u/mogoodrich)\ **Post date:** [November 20, 2019, 9:14pm UTC](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795/59 "2019-11-20T21:14:07Z")
Hello all… we’ve been testing against the 2.3.0-SNAPSHOT and have run into some interesting failing unit tests in one of our builds that will need some debugging. I’m guessing it has been caused by the change to the Person hibernate mapping. This test, which was previously passing, fails when run against 2.3.0-SNAPSHOT: > In this case, the “voided” patient is now returned in the query. Note that we void the patient in the first part of the test, so this may only be a problem that manifests itself during testing, but needs further exploring. Looking deeper, the following test in core still passes… > … but when I put a breakpoint at 1756 in debugger I’m seeing the following strange configuration which I suspect is causing the problem when running a search: ![2019-11-20_16-06](https://talk.openmrs.org/uploads/default/original/2X/7/7d463a4a75a190f22d5baf4195213455e4f16cff.png) ![2019-11-20_16-06_1](https://talk.openmrs.org/uploads/default/original/2X/4/40610a453b268f0aaf553345f3587f3ef33d4a18.png) But when I run this test in Core 2.2.x I see the following (which is what I would expect): ![2019-11-20_16-11](https://talk.openmrs.org/uploads/default/original/2X/0/01d1c4d697745004aeadb2e1a43831400a97dd7d.png) fyi @mksd @wyclif @dkayiwa @mseaton Take care, Mark ---
**Author:** ![mogoodrich](https://talk.openmrs.org/user_avatar/talk.openmrs.org/mogoodrich/32/3324_2.png) [@mogoodrich](https://talk.openmrs.org/u/mogoodrich)\ **Post date:** [November 20, 2019, 9:32pm UTC](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795/60 "2019-11-20T21:32:50Z")
Okay, so I see that we added a bunch of fields to the Patient object in order to apply the mappings as annotations instead of in a separate mapping file, and these fields are identical to fields already on BaseOpenmrsData which I assume is what is causing the problem: > [Previous page](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795.md?page=2) [Next page](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795.md?page=4)