Build: #106 failed Manual run from the stage: Release by Mike Seaton

Stages & jobs

  1. Build and Test

  2. Deploy

  3. Release

    Requires a user to start manually

Build result summary

Details

Completed
Queue duration
< 1 second
Duration
6 minutes
Labels
None
Revisions
Git
610bfa35e6c9d9e69e81049c99994a892b1a75a5
Release scripts
cebe6dcb943ff033576f2d65053e5ad420701213
Failing since
#103 (Changes by Dennis Kigen <kigen.work@gmail.com>)
Fixed in
#107 (Manual run from the stage: Release by Mike Seaton)
No failed test found. A possible compilation error occurred.

Responsible

This build has been failing since #103
No one has taken responsibility

Code commits

Git
Author Commit Message Commit date
Michael Seaton <mseaton@pih.org> Michael Seaton <mseaton@pih.org> 610bfa35e6c9d9e69e81049c99994a892b1a75a5 Revert changes to node and yarn versions for release

Error summary for Release to Maven

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

+ docker pull maven:3.9.9-amazoncorretto-8
+ docker run -v m2-repo:/root/.m2/repository -v /home/bamboo-agent/.m2/settings.xml:/root/.m2/settings.xml:ro -v /data/bamboo-agent/xml-data/build-dir/BM-BMM-RTM:/module -v /home/bamboo-agent/.ssh/github:/root/.ssh:ro -e GIT_USER_NAME=openmrs-bot -e GIT_USER_EMAIL=infrastructure@openmrs.org -e 'GIT_SSH_COMMAND=ssh -i /root/.ssh/id_rsa -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no' --rm -w=/module maven:3.9.9-amazoncorretto-8 bash -c '
    yum -y install git &&
    yum clean all &&
    git config --global user.email "$GIT_USER_EMAIL" &&
    git config --global user.name "$GIT_USER_NAME" &&
    git config --global --add safe.directory /module &&
    ./release-scripts/release-prepare-perform.sh \
      -r 7.0.0 \
      -d 7.1.0-SNAPSHOT \
      -e https://github.com/openmrs/openmrs-module-bedmanagement.git
  '
[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.