@abertnamanya and @mherman22 is this the build that you are referring to? OpenMRS Platform - OpenMRS Platform 2.6.x 13: Build result summary - OpenMRS Bamboo
1 Like
yes it was and i see now it’s passing.
What was the fix though? i ask because the error was something like – 5345.3 [ERROR] Failed to execute goal org.openmrs.maven.plugins:openmrs-sdk-maven-plugin:4.5.0:build-distro (build-distro-bundled) on project platform: Unable to find/resolve artifact.: Could not transfer artifact org.openmrs.web:openmrs-webapp:war:2.6.0-alpha-20221128.171008-1 from/to openmrs-repo (https://mavenrepo.openmrs.org/nexus/content/repositories/public): GET request of: org/openmrs/web/openmrs-webapp/2.6.0-alpha-SNAPSHOT/openmrs-webapp-2.6.0-alpha-20221128.171008-1.war from openmrs-repo failed: Connection reset
Connection reset is something caused by a problem with the internet connection. So i just rerun it. Can you meet with @abertnamanya and access where we are now? Is everything now as expected?
1 Like
yeah, sure!
i believe so, we are remaining with updating the version of CIEL in the standalone’s pom then we should be able to release the alpha.
@abertnamanya im pinging you on slack so that we assess
Sorry I was away but am back in action 
1 Like
@dkayiwa so we have attempted to update the ciel version in standalone pom but we are facing this blocker - standalone - Pastebin.com.
Steps we followed
-
forked and cloned GitHub - openmrs/openmrs-standalone: A simplified, all-inclusive installation option with both an embedded database and web server.
-
Then we downloaded the concept dictionary using the access that we received on dropbox.
-
Then we copied that zipped older into the root of openmrs-standalone directory.
-
Then triggered
mvn deploy:deploy-file -DgroupId=org.openmrs.contrib -DartifactId=ciel-dictionary -Dversion=2.3_20221104 -Dpackaging=zip -Dfile=openmrs_concepts_2.3_20221104.sql.zip -DrepositoryId=openmrs-repo-contrib -Durl=https://mavenrepo.openmrs.org/nexus/content/repositories/contribin the terminal
The error looks to be a 401-unauthorized as seen here → Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file (default-cli) on project standalone: Failed to deploy artifacts: Could not transfer artifact org.openmrs.contrib:ciel-dictionary:zip:2.3_20221104 from/to openmrs-repo-contrib (https://mavenrepo.openmrs.org/nexus/content/repositories/contrib): Transfer failed for https://mavenrepo.openmrs.org/nexus/content/repositories/contrib/org/openmrs/contrib/ciel-dictionary/2.3_20221104/ciel-dictionary-2.3_20221104.zip 401 Unauthorized -> [Help 1] …
cc: @abertnamanya
Before getting to that, is openmrs-core 2.6.0-alpha properly released?
Not yet, i am going to run the release stage for core now. Because everything looks set
cc: @abertnamanya
Can you do this together with @abertnamanya after discussing. This will help you avoid releasing versions like 2.5.9 instead of …
1 Like
I have pinged him already and im waiting for him so tht we get underway
Hi @dkayiwa this error keeps popping up whenever I try to release.
Here is the Core Plan link: OpenMRS Core - Openmrs Core 2.6.x 12: Build result summary - OpenMRS Bamboo
[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.
cc: @mherman22
@abertnamanya did you just delete the 2.6.0-alpha tag?
Yes, I did, actually, that error appears even when the tag does not exist.
Can you run the plan afresh and then ping me after the failure, before you delete the tag?
2 Likes
Delete the tag, run a new build, and release again. Then tell me what happens.
Same error coming again OpenMRS Core - Openmrs Core 2.6.x 16: Build result summary - OpenMRS Bamboo
[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.
I do not see the 2.6.0-alpha tag. Are you the one who deleted it?
I haven’t deleted the tag
@abertnamanya The message you’re reporting is mostly just noise. Note the part that says “scroll up the logs to see the error”. The relevant message is usually a few lines above that one, in this case:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5.1:rollback (default-cli) on project openmrs: An error is occurred in the checkin process: Exception while executing SCM command. Detecting the current branch failed: fatal: ref HEAD is not a symbolic ref -> [Help 1]
For this issue (and @jwnasambu, I think you reported something similar), the solution is generally to ensure that the “Use Shallow Clones” option for the repository (found in the Linked Repository configuration) is unchecked:
If someone can figure out how to modify this setting just for the release task and not every time, that would be a benefit.
PS This particular error happens when Maven tries to run the command to create the tag, so the 2.6.0-alpha tag was never created…
1 Like