Any idea if this something that could be looked at in the near future?
In the context of Bahmni we would like to make a maintenance release of EMR API 1.24.5. That would be off the 1.24.x branch. We can still do it manually of course.
In all fairness, I have the feeling that HEAD of any branch might work. What I know it won’t work is if it’s not the head of the branch (like a previous commit) on the current branch.
@cintiadr I tried to launch the release process off the revision 1.24.x but it fails (see here):
Checkout to revision 1.24.x has failed.command /usr/bin/git checkout -f 1.24.x failed with code 1.
Working directory was [/home/bamboo-agent/bamboo-agent/xml-data/build-dir/EMRAPI-EMRAPI-JOB1].,
stderr: error: pathspec '1.24.x' did not match any file(s) known to git.
It looks like the local env. doesn’t know yet about that branch. A git fetch beforehand could help, is there a way to do that?
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project emrapi:
Failed to deploy artifacts:
Could not find artifact org.openmrs.module:emrapi:pom:1.24.5 in openmrs-repo-modules (http://mavenrepo.openmrs.org/nexus/content/repositories/modules) -> [Help 1]
I can see that the release from branch XYZ-123 appears to have worked as expected, which is really great to know.
That’s because someone changed the repository configuration instead of creating a branch build. I don’t understand how one was pointing to master, but I don’t really care at this point.