Proposal for Limited Scope RefApp 2.13 & request for Release Manager

,

@jwnasambu i have deleted it. Sorry for the delay. I had not seen this because the talk email notifications have not been working for the last two days.

You don’t have to be sorry! its not your fault . Am so grateful you are always so helpful. Thanks for being a blessing to me.

@dkayiwa Kindly help please on steps on how to create a UAT server please! I have searched for the guide but all in vain. I have tried out something but not working as expected.

Run this plan: OpenMRS environments - Reset uat-refapp: Plan summary - OpenMRS Bamboo

I have run and its successful as reflected here OpenMRS environments - Reset uat-refapp 2169: Build result summary - OpenMRS Bamboo

I have just created a new one.

Deploy using this: Log in as a Bamboo user - OpenMRS Bamboo

On the deployment preview screen, select Create new release from build result and then select the latest build result of the 2.x reference application distribution.

This is what I have come up with Bamboo error reporting - OpenMRS Bamboo.

It looks correct.

1 Like

@dkayiwa, @ibacher I am trying to release a docker image for Reference Application 2.13.0-alpha but running into this build failure Reference Application - Distribution 2.x 13496: Build result summary - OpenMRS Bamboo. Besides, this is my deployment link Log in as a Bamboo user - OpenMRS Bamboo just wondering if its well set. Kind help on the way forward please! Am sorry I haven’t come a cross any guide on creating the Reference Application UAT but things have have to work at the end of the day.

Looks like you’re trying to create a tag that already exists as can be seen here → [ERROR] fatal: tag '2.13.0-alpha' already exists hence leading up to Delete the tag from the repository (if it exists), check if the SCM tag is a ssh and not http and try again which can be overcome by deleting the tag at Release 2.13.0-alpha · openmrs/openmrs-distro-referenceapplication · GitHub.

You are right! I don’t have the deleting rights that is what I requested for help from here.

1 Like

Tag deleted.

Is it my internet or the nature of the build. This build has been running Reference Application - Distribution 2.x 13497: Build result summary - OpenMRS Bamboo since morning the day is almost ending its running. I even pretented you delete the tag maybe by then it will be complete but wah! Is my internet safe! :rofl: :rofl: :rofl:

The build in your link above is green :slight_smile:

Am forced to climb a tree. Internet is so bad in my location today I have been running this build since 3.59pm.

@dkayiwa Kindly am sorry for a bother. Help me delete the 2.13.0-alpha tag

@jwnasambu Just try releasing it as 2.13.0-alpha.1. That’s a valid version number and won’t interfere with the existing 2.13.0-alpha tag…

Thanks so much! am crossing my fingers for the next release hopefully I won’t have a long list of failed build with many tags.

@dkayiwa, @ibacher I have managed to release 2.13.0-alpha.4 as reflected on this build. This my observation:

  • war file wasn’t released,
  • 2.13.0-alpha.4 release is not reflected on docker hub tags.
  • I reset the UAT server after the release but still the legacy UI reflects the server is running on platform 2.6.0 contrary to 2.5.9.
    Lastly, when I click on system information the page is empty yet its supposed to reflect all the modules in this version and their latest version. Kindly what could be the cause of all these issues?

N/B : on the QA server, all modules version reflects what is in the pom.xml file and the server is running on platform 2.5.9 version as expected. Just wondering how to fix the UAT server to match the QA server.

Given that the build did not complete, if i were you, i would run a new one.