Yes… I don’t think there’s a secure way to allow this to be done through Bamboo. I’ve reapplied the fix for this. PS, we need to be a little careful with these jobs. The 2.6.x branch was publishing dev images called 2.5.x-dev…
IMO Since OpenMRS_Platform_2.6.0-alpha is already out, all you wanna do is set a timeline for it, invite testers for the features you released from the community, including yourself. using your UAT server.
and update the RoadMap for 2.6.0 Issues,(I can see the wiki for alpha is done good Job !)
After that is done, collect anything missing and prepare beta, if there are no more issues, and if all is well , then prepare for 2.6.0
i have gone through a couple of resources on UAT Platform and none seems to really describe how testing of platform can be done on the UAT Platform Server.
Any help rendered to me in that regard is highly welcome @tendomart@kdaud
@mherman22 Nothing really hard, the Idea is look at the Tickets done at your Release notes page, those are things you need to test, using the Refapp.
Some are deployment Issues and may require a local setup or a remote setup to test the container state instance it’s self like [TRUNK-6083] Build and deploy docker image for openmrs-core - OpenMRS Issues, for such an issue, you can pull the image and spin a container on your local machine or still setup the container on one of the remote servers on the openmrs infra.
We are getting the following when we try to release core 2.6.0-beta to maven.
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project openmrs: Failed to deploy artifacts: Could not find artifact org.openmrs:openmrs:pom:2.6.0-beta in openmrs-repo-releases (https://mavenrepo.openmrs.org/nexus/content/repositories/releases) -> [Help 1]