Looking for the OpenMRS 2.6.0 Platform Release Manager

Development
, , ,
61

thanks @ibacher for this elaborative answer

62 
mvn release:perform failed. Fix the problem and try another release number.

we have this error though this time round the 2.6.0-alpha tag is created in core.

Failing plan - OpenMRS Core - OpenMRS Core 2.6.x 21: Build result summary - OpenMRS Bamboo

we tried this suggestion by @ibacher but the error changed to the above stated error as shown in the full error log here.

cc: @abertnamanya @ibacher @dkayiwa

63

Run a new build and tell us what happens.

64

Here is the failing plan OpenMRS Core - Openmrs Core 2.6.x - Release to maven 22: Job result summary - OpenMRS Bamboo

No failed test found. A possible compilation error occurred

cc: @dkayiwa @abertnamanya

65

@ibacher this looks like the permission denied issue that you raised on the infra channel.

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-install-plugin:2.4:install (default-install) on project openmrs: Failed to install artifact org.openmrs:openmrs:pom:2.6.0-SNAPSHOT: /home/bamboo-agent/.m2/repository/org/openmrs/openmrs/2.6.0-SNAPSHOT/openmrs-2.6.0-SNAPSHOT.pom (Permission denied) -> [Help 1]

66

Thank you @dkayiwa @ibacher , How can we solve the issue of permissions.

67

From @ibacher

So, I think the release task for 2.6.0 (and onwards) needs to be re-written to use Docker. Even if I change the file permissions (the “temporary” fix), the release will still fail because the version of 2.6.0-SNAPSHOT will be the one built as part of the same job.

@raff does this, by any chance, happen to be on your radar? :slight_smile:

68

We walked through this on the Platform Team call and Ian helped identify a solution (constraining Docker’s access only to the settings.xml file that’s needed). We’ve implemented that solution and the build is now successful!

2 Likes
69

OpenMRS Core - OpenMRS Core 2.6.x 24: Build result summary - OpenMRS Bamboo has built successfully and tag has been created successfully at Release 2.6.0-alpha · openmrs/openmrs-core · GitHub.

cc: @abertnamanya

70

Hi @dkayiwa, The release of core 2.6-aplha was successful, now we are on the step of updating standalone to the latest CIEL but its giving 401 Unauthorized when we run

mvn deploy:deploy-file -DgroupId=org.openmrs.contrib -DartifactId=ciel-dictionary -Dversion=2.3-2022-11-04 -Dpackaging=zip -Dfile=openmrs_concepts_2.3_20221104.sql.zip -DrepositoryId=openmrs-repo-contrib -Durl=JFrog

CC: @mherman22

71

You accidentally released this as 2.5.9 resulting into a 2.5.9 release that does not come from the 2.5.x branch. Hence this problem: Slack

72

my apologies, how do we go about rectifying the damage caused?

cc: @abertnamanya

73

I have deleted the tag and also cleared it from the artifact repository.

1 Like
74

Thanks, so everything else is okay in regards to the core 2.6.0-alpha?

75

Thanks @dkayiwa , Actually everything now looks good. Commits · openmrs/openmrs-core · GitHub

76

Which build?

77

Sorry I cross checked I had thought the commit had 2.5.9 but it looks good

78

@dkayiwa should we now run platform build?

79

Didn’t you get asked for credentials for JFrog?

80

No where was showing to provide any credentials, Do I need to create a ticket with helpdesk?

CC: @mherman22