Can you share your local server side log after loading the addon manager?
True…let me get back…
You mean during deployment?
extracted from OpenMRS Platform - OpenMRS Platform - 2.5.x - Release to maven 21: Build log - OpenMRS Bamboo
Your local server log.
They are WARN - Module.expandExtensionNames(573) |2021-10-27T14:30:56,912| webservices.re - Pastebin.com
and
The same was true for 2.3.0
@dkayiwa looking at the logs
Did you find out any other probable cause ?
I also noticed the server has "Settings, upload and check updates are disabled from the website at this time. The runtime property module.allow_web_admin must be set to true. "
Is there a way of manipulationg the openmrs-runtime.properties on yokobue.openmrs.org ? I could not find anyway like ssh
Hey @dkayiwa can you grant me write access to GitHub - openmrs/openmrs-distro-referenceapplication
I need to create a Branch for platform 2.5.x so we can begin the process of spinning 2.12.0 on it.
I managed to build 2.13.0-SNAPSHOT on 2.5.0-alpha.3 with success excluding tests.
And still running on Docker
Did the write permission help you?
Yes it was of help …Iam actually trying to spin up the instance (2.13.0-SNAPSHOT )
As always it’s standalone impeding things here
build 31-Oct-2021 14:50:40 [ERROR] Failed to execute goal org.liquibase:liquibase-maven-plugin:3.8.9:update (empty-database-create-schema) on project referenceapplication-standalone: Execution empty-database-create-schema of goal org.liquibase:liquibase-maven-plugin:3.8.9:update failed: **An API incompatibility was encountered while executing org.liquibase:liquibase-maven-plugin:3.8.9:update: java.lang.NoSuchMethodError:** liquibase.exception.ValidationErrors.checkRequiredField(Ljava/lang/String;Ljava/lang/Object;)Lliquibase/exception/ValidationErrors;
Will you feel good if we skipped for testing this one ?
Aren’t you supposed to be using refapp.version=2.12.0?
Yes , that is what i used previously …But there was a break in things. Apparently the build could not find the artifact 2.12.0 from Maven …So i wondered how that was ,after @herbert24 finished the release.
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project referenceapplication: Failed to deploy artifacts: Could not find artifact org.openmrs.distro:referenceapplication:pom:2.12.0 in openmrs-repo-releases (JFrog) → [Help 1]
are you trying to use the sdk,@tendomart if so,have you tried that process lately?
@tendomart from the log that you have referenced above, i see this [INFO] Uploading: https://mavenrepo.openmrs.org/nexus/content/repositories/releases/org/openmrs/distro/referenceapplication/2.12.0/referenceapplication-2.12.0.pom which means that you tried to deploy it to jfrog but it already existed as released by @herbert24. I also noticed that your bamboo build had also tried to again release reference application 2.12.0 and had updated the distro pom.xml file (which i have just reverted).
2 Likes
Yes , and that was on the main branch .The Hacky way i had come up with was creating Branch 2.12.0-dev and changing the corresponding Bamboo variable to be refapp.version=2.12.0-dev
So That’s why i had opted for 2.13.0-SNAPSHOT , with non-snapshot modules… Which worked , but again broke Standalone.
That also switched the https://qa-refapp.openmrs.org/ from platform 2.4.0 to 2.5.0.alpha3 and hence this: Automated test for booking an appointment catches a bug
2 Likes
@tendomart in simple terms, your new bamboo build should not deploy to qa-refapp.
I need to create a new Branch at GitHub - openmrs/openmrs-standalone: A simplified, all-inclusive installation option with both an embedded database and web server. so i can change some params… Otherwise standalone is facing some API Compatibilities. The other option is to disable it from my [Plan](https://Configuration - Refapp 2.12.0-dev )
Something with Liquibase not yet known here
You could just fix the deployment server. When that is done, it does not matter whether the standalone is successfully built or not.