Build: #45 was successful

Job: Release to Maven did not start

Stages & jobs

  1. Test module

  2. Release

    Requires a user to start manually

Code commits

Git

  • dkayiwa <kayiwadaniel@gmail.com>

    dkayiwa <kayiwadaniel@gmail.com> 2350d99797ba386c5ba5b01fd7c471ea0414a462

    Increasing the node and npm versions

    • owa/package.json (version 2350d99797ba386c5ba5b01fd7c471ea0414a462)

Release scripts

  • Burke Mamlin <burke@openmrs.org>

    Burke Mamlin <burke@openmrs.org> 681f3bff12454842e7e4fae01a15ce2827d75dc7

    Fix sourceforge rsync transfers
    Sourceforge key is now under a sourceforge subfolder. Use "openmrs" username.

    • scp-to-sourceforge.sh (version 681f3bff12454842e7e4fae01a15ce2827d75dc7)
  • Ian Bacher

    Ian Bacher 1969d1c2650fc66ab14f5edb4052a329a196f370

    Update release-prepare-perform.sh
    Hopefully fix the regex issue

    • release-prepare-perform.sh (version 1969d1c2650fc66ab14f5edb4052a329a196f370)
  • Ian Bacher

    Ian Bacher 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

    • release-prepare-perform.sh (version ce18ee46b521ba3039496ba220aeddd4b313c5e5)