OCL API 2
Build: #2338 failed
Job: Release failed
Job result summary
- Completed
- Duration
- 3 minutes
- Agent
- xiao.openmrs.org (2)
- Revision
-
b9d9e33dbf9460453137ced66185f9f23a7a24a7
- Fixed in
- #2339 (Manual run from the stage: Release by Sunny Aggarwal.)
Error summary
The build generated some errors. See the full build log for more details.
+ set +x
WARNING! Using --password via the CLI is insecure. Use --password-stdin.
WARNING! Your password will be stored unencrypted in /home/bamboo-agent/.docker/config.json.
Configure a credential helper to remove this warning. See
https://docs.docker.com/engine/reference/commandline/login/#credential-stores
Switched to a new branch 'release'
To github.com:OpenConceptLab/oclapi2.git
* [new tag] 2.3.191-b9d9e33d -> 2.3.191-b9d9e33d
Switched to branch 'master'
To github.com:OpenConceptLab/oclapi2.git
! [rejected] master -> master (fetch first)
error: failed to push some refs to 'github.com:OpenConceptLab/oclapi2.git'
hint: Updates were rejected because the remote contains work that you do
hint: not have locally. This is usually caused by another repository pushing
hint: to the same ref. You may want to first integrate the remote changes
hint: (e.g., 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.
WARNING! Using --password via the CLI is insecure. Use --password-stdin.
WARNING! Your password will be stored unencrypted in /home/bamboo-agent/.docker/config.json.
Configure a credential helper to remove this warning. See
https://docs.docker.com/engine/reference/commandline/login/#credential-stores
Switched to a new branch 'release'
To github.com:OpenConceptLab/oclapi2.git
* [new tag] 2.3.191-b9d9e33d -> 2.3.191-b9d9e33d
Switched to branch 'master'
To github.com:OpenConceptLab/oclapi2.git
! [rejected] master -> master (fetch first)
error: failed to push some refs to 'github.com:OpenConceptLab/oclapi2.git'
hint: Updates were rejected because the remote contains work that you do
hint: not have locally. This is usually caused by another repository pushing
hint: to the same ref. You may want to first integrate the remote changes
hint: (e.g., 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.