Last minute rudimentary testing for Platform 2.3.2

dkayiwa · September 28, 2020, 5:25pm

Did you specify it exactly as such?

jwnasambu · September 28, 2020, 5:28pm

Yes . I used 2.3.3

dkayiwa · September 28, 2020, 5:36pm

It is supposed to be 2.3.3-SNAPSHOT

jwnasambu · September 28, 2020, 5:38pm

Thanks so much for the clarification! I really appreciate your help.

jwnasambu · September 29, 2020, 10:11am

@dkayiwa After making the changes, I re-run the release stages again but the build on Release to maven did not complete as reflected by this error logs https://pastebin.com/3DR3uStP and I want to think its because the release had already taken place on openmrs-distro-platform/ pom.xml as reflected on the commit history on platform 2.3.x branch on github and by re-running the release stages again the release to maven couldn’t build which may be the cause why this release is not reflected on the file listing page on Sourceforge. Kindly help on how to make the release appear on the sourceforge!

dkayiwa · September 29, 2020, 4:14pm

Could not find artifact org.openmrs.web:openmrs-webapp:war:2.3.3.

Are you specifying version 2.3.3 anywhere?

jwnasambu · September 29, 2020, 4:18pm

I specified it very well. Its on the core where I had forgotten to specify but I fixed it by raising a pull request.

dkayiwa · September 29, 2020, 4:42pm

But we have never released version 2.3.3

jwnasambu · September 29, 2020, 4:46pm

I only used 2.3.3 as maven.development.version snapshot but what am releasing is 2.3.2.

dkayiwa · September 29, 2020, 4:55pm

Did you just miss this?

jwnasambu · September 29, 2020, 5:02pm

In my explanation I missed it but in my changes I used maven.development.version 2.3.3-SNAPSHOT which failed to release on maven when I re-ran the release stages.

jwnasambu · September 29, 2020, 5:11pm

@dkayiwa I wouldn’t mind making the changes and re-run the release steps again.

jwnasambu · September 29, 2020, 6:03pm

@dkayiwa sorry for a bother! I am trying to cross check where I missed out and just to confirm that I used the right version, this this how my pom.xml looks likes.

jwnasambu · September 30, 2020, 11:46am

@dkayiwa When I release on openmrs-platform 2.3.x from CI by running the Release stage , the Release to Maven stage is failing with this error

 [ERROR] mvn release:prepare failed. Attempting to do a release rollback.    
 [ERROR] mvn release:prepare failed, scroll up the logs to see the error. release:rollback was attempted. Delete the tag from the repository (if it exists), check if the SCM tag is a ssh and not http and try again.

Which I want to believe is due to already created branch via previous runs. Since I want to run it again can cleaning be of help?

jwnasambu · October 12, 2020, 11:32am

@cintiadr and @dkayiwa am glad platform 2.3.2 is now appearing on file listing page on Sourceforge which wasn’t happening for the last couple of weeks when I tried to release the platform. The challenge am facing now is when I open the recent released version, which is 2.3.2 I can’t access the standalone to expand the details of the uploaded ZIP file. Could this be because I failed to Release to maven? How can I go about it to fix the missing ZIP file?

cintiadr · October 13, 2020, 1:07am

It’s hard to help without context. What happened?

Did you remove the branch and reran the release?

Would you have a link to the build, so we can investigate both the upload to sourceforge and the artefact generate?

jwnasambu · October 13, 2020, 12:44pm

@cintiadr thanks for looking into this issue. I 'm following this guide to release platform 2.3.2 version. I was able to release the core on bamboo successfully but platform 2.3.x failed to Release to Maven throwing this error.

 [ERROR] mvn release:prepare failed. Attempting to do a release rollback.    
 [ERROR] mvn release:prepare failed, scroll up the logs to see the error. release:rollback was attempted. Delete the tag from the repository (if it exists), check if the SCM tag is a ssh and not http and try again.

The pom.xml content was okay same applies to the history. The SDK works pretty well but the file wasn’t reflected on the Sourceforge since 2020-09-22T21:00:00Z and I have never removed the branch to re-run the release. Yesterday I was able to see the release appearing on the Sourceforge and I thought maybe it was as a result of your routine troubleshooting. This is the link to the latest build.

Thanks in advance.

cintiadr · October 14, 2020, 7:12am

Juliet Wamalwa, we need to get the release done.

We need a green build. Prepare failed, we lost all the logs (as time and builds ran after), so I cannot tell why it failed.

So let’s do this.

Remove tag platform-2.3.2 from the git repository:

After that, let’s try to run the release again. If it doesn’t work, can you please copy the logs to binpaste? When we fix this build, we can actually investigate the rest.

jwnasambu · October 14, 2020, 9:41pm

@dkayiwa this is the screensho

Am not able to see the delete button.

jwnasambu · October 14, 2020, 11:49pm

@cintiadr I removed platform-2.3.2 tag from the git repository then ran release stages which ended up with the a compilation error with this logs

   Error summary for [Release to maven](https://ci.openmrs.org/browse/OP-OPM7-RTM-98/)

The job generated some errors, drill down into the **[full build log](https://ci.openmrs.org/browse/OP-OPM7-RTM-98/log)** for more details.

[ERROR] mvn release:prepare failed. Attempting to do a release rollback.
[ERROR] mvn release:prepare failed, scroll up the logs to see the error. release:rollback was attempted. Delete the tag from the repository (if it exists), check if the SCM tag is a ssh and not http and try again.

on this build link https://ci.openmrs.org/browse/OP-OPM7-98.