When I search for the reporting module in modulus, I get two hits for “reporting”. When I click on one of them it looks like someone has managed to create a duplicate entry with the latest version of the reporting module. Not sure what happened here:
Is anyone working on maintaining modulus? I tried uploading a module twice but it does not show up and yet the upload does not give any error message. Modulus in general seems to need some love!
I’ve never touched Modulus on the administrative side…I do not think anybody reported this specific case to helpdesk – but not sure as far as I’ve been able to see – we’ve had a few things reported about duplicate modules published on Modulus, too lazy to look now but not sure if it’s related to this.
@darius, aren’t you in the Owners group on github, and therefore have access to all repos to do this? We should however test it in staging (you can deploy to staging from Bamboo as well I believe?)
I have the privileges to change a tag in github, but I have zero insight into why the tags are set the way they are, and why the master branch isn’t yet deployed to production. So, I don’t want to touch anything unless any of these happen:
@elliott tells us what the current state is and why
someone else who has this info speaks up (or @elliott tells us who else that would be)
we realize that literally nobody owns this, and nobody knows the exact state
I haven’t touched the state since 2014. But I poked around again in Bamboo and can provide this on how things are set up:
master` gets built by Bamboo every time a commit is pushed.
There are two deploy plans for Modulus Core (the grails app): one for modules-stg.openmrs.org, the other for modules.openmrs.org. These are run manually using any build of Modulus from Bamboo.
Modulus UI has a similar set of deploy projects.
The prod branch is the repository is outdated and should be removed. The staging and production tags were once used to select the version used to build for stg and prod, but this has been disabled in Bamboo. I don’t know if I disabled this or someone else did.
Currently modules-stg.openmrs.org is down (even Tomcat is unreachable). I’d like to see the build from master deployed there first, and then I think we should update prod.
I used bamboo to deploy the latest modulus-ui build to the staging server. (Logs here.)
@elliott (or @r0bby), do you know if the modules-stg server is pointing at the prod database, or if it has its own?
The owner and maintainers appear null on the one module I looked at: https://modules-stg.openmrs.org/#/show/119/reporting but I don’t know if that’s a demo data issue or something else. And I don’t seem to have administrator power on this staging server (or, I don’t see additional links I was expecting).
If that’s easy to do, sure! More valuable would be ensuring that I have the same privileges on modules-stg as on modules so that I can confidently test things like deleting modules.