Travis ci 无法将部署从Travis ci推送到cloudcontrol

Travis ci 无法将部署从Travis ci推送到cloudcontrol,travis-ci,cloudcontrol,Travis Ci,Cloudcontrol,无法使用Travis CI将部署从Github存储库推送到CloudClocontrol,以下是日志: Deploying application Warning: Permanently added 'cloudcontrolled.com' (RSA) to the list of known hosts. To ssh://xxx.git ! [rejected] HEAD -> master (fetch first) error: failed to push so

无法使用Travis CI将部署从Github存储库推送到CloudClocontrol,以下是日志:

Deploying application
Warning: Permanently added 'cloudcontrolled.com' (RSA) to the list of known hosts.
To ssh://xxx.git
! [rejected]        HEAD -> master (fetch first)
error: failed to push some refs to 'ssh://awesomeblog@cloudcontrolled.com/repository.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
有没有办法强制硬推覆盖远程git的状态


如果您需要查看完整日志,可以在此处找到。请注意,相关日志在末尾。

我通过Travis CI发布的新功能解决了这个问题

他们在部署期间推送时添加了-f选项

您只需添加

edge: true

Cloudcontrol部署选项,如本文所述,在您的yml文件中

那么,您是否按照请求执行了git拉入?两个存储库处于完全不同的状态,执行拉入会有危险吗?此外,在部署到Heroku和Openshift时,我也遇到过类似的情况,Heroku/Openshift的git状态与我的github repo的状态完全不同,但它仍然能够通过硬推来部署代码,这是相互作用的:如果拉是危险的,那么推也是危险的。我真的看不出还有什么其他方法。我会用你当前的代码用
git push-f
手动推一次到云控制,然后travis ci应该可以再次推。