UI Commons build locally fails with 503

Tags: #<Tag:0x00007f302bd8a4e8>

The mvn install for the openmrs-module-uicommons seems to be failing with a 503 error.

The failure:

Failed to transfer file http://rubygems-proxy.torquebox.org/releases/rubygems/sass/3.1.0/sass-3.1.0.pom with status code 503

I did a quick search and looks like the rubygems-proxy server is not being maintained anymore and we might have to switch to an alternate server. https://github.com/torquebox/rubygems-servlets/issues/20

Any idea how to fix this problem?

CC: @mksd @mksrom @dkayiwa @ssmusoke

1 Like

Is the same failure happening on the bamboo CI plan?

@dkayiwa

If you are referring to the travis-ci pipeline (https://travis-ci.org/openmrs/openmrs-module-uicommons), this one is passing, but the reason could be it is getting the old jars from local maven cache. Not sure if that is the way it is configured, just a guess.

That is an issue I have noticed in Bahmni as well. It has been 1 month or so that this repo is down. (cc @angshuonline)

Bamboo is working but that doesn’t mean it’s ok, some stuff might have been cached locally for a while. Travis is a better source of truth IMO.