dpl: Bintray deployment: uploading failed but deployment succeeds
Uploading debian packages to bintray has failed with code 400 but overall result of the deployment is still success for some reason and the build is marked as succeeded.
Expected result: if uploading any of the files fails then deployment should be interrupted and exit code should not be 0 (success).
Here is the log: https://travis-ci.org/igagis/stob/jobs/126350018
Excerpt from log:
[Bintray Upload] Reading descriptor file: travis_bintray.json
[Bintray Upload] Uploading file '../libstob-dev_3.2.0_amd64.deb' to libstob-dev_3.2.0_amd64.deb
[Bintray Upload] Bintray response: 400 Bad Request. Error occurred while uploading
[Bintray Upload] Uploading file '../libstob-doc_3.2.0_all.deb' to libstob-doc_3.2.0_all.deb
[Bintray Upload] Bintray response: 400 Bad Request. Error occurred while uploading
[Bintray Upload] Uploading file '../libstob1-dbg_3.2.0_amd64.deb' to libstob1-dbg_3.2.0_amd64.deb
[Bintray Upload] Bintray response: 400 Bad Request. Error occurred while uploading
[Bintray Upload] Uploading file '../libstob1_3.2.0_amd64.deb' to libstob1_3.2.0_amd64.deb
[Bintray Upload] Bintray response: 400 Bad Request. Error occurred while uploading
[Bintray Upload] Publishing version 'all' of package 'libstob'...
[Bintray Upload] Bintray response: 200 OK.
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 18 (8 by maintainers)
We recommend using JFrog CLI for Bintray deployment. It is very popular, regularly maintained, includees much more functionality and is easier to work with.
Will do @haphut.
Please fix this in the documented provider or remove the provider from Travis CI altogether. At least add a big warning at the top saying that this provider cannot be relied on in a CI/CD pipeline.
Got it @igagis. We’ll submit a pull request to fix this. BTW, JFrog CLI has been released recently and it can also be used from Travis-CI for Bintray and Artifactory uploads, downloads and more.
@igagis, by “does not handle any errors”, do you mean that it does not stop in case one of the requests fails? (in this case with HTTP response 400).
@eyalbe4 actually no, it dies not. It was working before and then it stopped without any reason. Anyway, now it seems working again.
The problem reported by this bug is that travis-ci Bintray provider does not handle any errors.