Agreed. As I was writing the post, I was already thinking there’s little need for a staging environment at this point. Starting with a qa & demo makes sense. Actually, if we follow the path of RefApp CI, the next next environment we’ll likely want would be uat (i.e., user acceptance testing = an environment for testing of features/changes that is safe from automated/unexpected changes but not yet ready for the demo site). But let’s start by focusing on an automated qa first (an automated version of what openmrs-spa is doing now).
@mksrom / @dkayiwa / @ibacher,
When I checkout the 3.x branch of openmrs-distro-referenceapplication and run mvn clean package, it fails with this error:
[ERROR] Failed to execute goal on project openmrs-distro-package: Could
not resolve dependencies for project
org.openmrs:openmrs-distro-package:pom:1.0.0-SNAPSHOT: Failed to
collect dependencies at org.openmrs.web:openmrs-webapp:war:2.3.3:
Failed to read artifact descriptor for
org.openmrs.web:openmrs-webapp:war:2.3.3: Could not transfer artifact
org.openmrs.web:openmrs-webapp:pom:2.3.3 from/to
maven-default-http-blocker (http://0.0.0.0/): Blocked mirror for
repositories: [openmrs-repo
(http://mavenrepo.openmrs.org/nexus/content/repositories/public,
default, releases+snapshots), archetype
(http://mavenrepo.openmrs.org/nexus/content/repositories/public,
default, releases+snapshots), openmrs-repo-thirdparty
(http://mavenrepo.openmrs.org/nexus/content/repositories/thirdparty,
default, releases+snapshots)]