Build #45

Build: #45 failed Manual run from the stage: Release by Mark Goodrich

Stages & jobs

  1. Default Stage

  2. Release

    Requires a user to start manually

Build result summary

Details

Completed
Duration
34 minutes
Labels
None
Revisions
Git
09fd91bd4d102dd7f9f52f1e7af59ead42672cc3 09fd91bd4d102dd7f9f52f1e7af59ead42672cc3
Release scripts
1969d1c2650fc66ab14f5edb4052a329a196f370 1969d1c2650fc66ab14f5edb4052a329a196f370
Total tests
136
Fixed in
#47 (Manual run from the stage: Release by Mark Goodrich)
No failed test found. A possible compilation error occurred.

Tests

  • 0 New failures
  • 0 Existing failures
  • 0 Fixed

Responsible

No one has taken responsibility for this failure

Code commits

Git
Author Commit Message Commit date
dkayiwa <kayiwadaniel@gmail.com> dkayiwa <kayiwadaniel@gmail.com> 09fd91bd4d102dd7f9f52f1e7af59ead42672cc3 09fd91bd4d102dd7f9f52f1e7af59ead42672cc3 Fix xml errors in Spring 5
Release scripts
Author Commit Message Commit date
Ian <52504170+ibacher@users.noreply.github.com> Ian <52504170+ibacher@users.noreply.github.com> 1969d1c2650fc66ab14f5edb4052a329a196f370 1969d1c2650fc66ab14f5edb4052a329a196f370 Update release-prepare-perform.sh
Hopefully fix the regex issue
Ian <52504170+ibacher@users.noreply.github.com> Ian <52504170+ibacher@users.noreply.github.com> ce18ee46b521ba3039496ba220aeddd4b313c5e5 ce18ee46b521ba3039496ba220aeddd4b313c5e5 Update release script to support semvers (#7)
* Uses a POSIX-compatible version of the regex for identifying semvers
* Reserves the ending -SNAPSHOT for development versions so we don't break the logic that follows

See: https://talk.openmrs.org/t/easing-semver-constraint-on-releasing-modules-from-bamboo/27716/2

Error summary for Release to module

The job generated some errors, drill down into the full build log for more details.

[ERROR] mvn release:prepare failed. Attempting to do a release rollback.
[ERROR] mvn release:prepare failed, scroll up the logs to see the error. release:rollback was attempted. Delete the tag from the repository (if it exists), check if the SCM tag is a ssh and not http and try again.