There are failing builds here that need attension ,https://ci.openmrs.org/browse/LBAC-LBAC/latest and https://ci.openmrs.org/browse/REFAPP-OMODDISTRO/latest cc @dkayiwa @cintiadr
Hi,
This one failed with a pretty clear message: https://ci.openmrs.org/browse/LBAC-LBAC-41/log
[ERROR] Tag 0.2.0 already exists in the repo. Delete it before we can continue with the process.
Maybe you want @suthagar23 to explain what happened?
The refapp distro seems to be failing the tests, so it’s not something I can probably help you with.
Hey,
Actually I triggered the release with new build from JIRA for a already released version of LBAC module. We can ignore this as it was already released successfully. Sorry for the mistakes.
Then by now, the latest release is Release-42 (https://ci.openmrs.org/browse/LBAC-LBAC-BTM-42) which was manually triggered by @dkayiwa. Thanks @dkayiwa
Hi @dkayiwa
Nope I didn’t notice that.
Seems like the appoinment shceduling ui update to latest cause the build error @ssmusoke
Can this be because of the build failure appointment scheduling module had.(npm issue).I fixed that in last week but new there was no successful build since 27 th.
yes @dkayiwa seems like selenium test cases are failing
https://travis-ci.org/openmrs/openmrs-distro-referenceapplication/jobs/577538004
Hi @dkayiwa
Hi daniel there are some issues am addressing currently It’s almost finished then I can have a look on the build failure issue.Sometimes these changes on coreapp which am working on may resolve the build issue as well.Will keep u updated.
Regards Ayesh
@ayesh can you raise a pull request on the reference app distro, https://github.com/openmrs/openmrs-distro-referenceapplication, with the snapshot versions of the modules that we have been working on as this may also be an issue why we are not seeing changes on qa-refapp
Hi @ssmusoke
I noticed still the test failures are there.Can it be the reason for not releasing to the staging(qa-ref-app) by ci ?
and one quick question @ssmusoke after the release module dependencies do need an update rightt?
For an example
this is registration app pom file.This has below dependencies if u look at the file
<properties>
<openMRSVersion>1.9.9</openMRSVersion>
<uiframeworkVersion>3.9</uiframeworkVersion>
<appframeworkVersion>2.9</appframeworkVersion>
<springVersion>3.0.5.RELEASE</springVersion>
<idgenVersion>4.4.0</idgenVersion>
<uicommonsVersion>2.4.0</uicommonsVersion>
<emrapiVersion>1.18</emrapiVersion>
<calculationVersion>1.2</calculationVersion>
<providerManagementVersion>2.5.0</providerManagementVersion>
<registrationcoreVersion>1.8.0</registrationcoreVersion>
<reportingModuleVersion>0.10.4</reportingModuleVersion>
<addresshierarchyVersion>2.9</addresshierarchyVersion>
<htmlformentryVersion>3.3.0</htmlformentryVersion>
<appuiVersion>1.7</appuiVersion>
<coreappsVersion>1.11.1</coreappsVersion>
<serializationXstreamModuleVersion>0.2.12</serializationXstreamModuleVersion>
<eventVersion>2.5</eventVersion>
<groovyVersion>1.8.7</groovyVersion>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
</properties>
Like wise in modules, there are dependencies.If am right we have to update them to the latest snapshot (only the modules we worked on) for our changes to take place?
@ayesh Let us start with the reference application distro, for qa-refapp then move to the individual modules
got it I will send a pr with the modules latest snapshots that we changed