当推送到OpenShift时,我得到预接收挂钩拒绝

时间:2022-08-26 19:15:26

I'm having trouble pushing to my OpenShift account. On first push I got this:

我无法推送到我的OpenShift帐户。第一次推动我得到了这个:

Counting objects: 2, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (2/2), 321 bytes | 0 bytes/s, done.
Total 2 (delta 1), reused 0 (delta 0)
remote: Not stopping cartridge nodejs because hot deploy is enabled
remote: Not stopping cartridge mongodb because hot deploy is enabled
remote: No such file or directory - /var/lib/openshift/54f614834387ec5dbe000201/app-deployments/2015-04-30_16-45-12.229/repo/node_modules/bower/node_modules/insight/node_modules/configstore/node_modules/user-home
To ssh://54f614834387ec5dbe000201@nodejs-fightersconnect.rhcloud.com/~/git/nodejs.git/
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'ssh://54f614834387ec5dbe000201@nodejs-abcaaaa.rhcloud.com/~/git/nodejs.git/'

Now when I push my git reports 'Everything is up to date' but my changes are not populated. It seems like an issue with OpenShift but I haven't received any response from them yet. Is there anything I can do to fix it?

现在,当我推送我的git报告“一切都是最新的”但我的更改没有填充。这似乎是OpenShift的一个问题,但我还没有收到任何回复。我能做些什么来解决它吗?

2 个解决方案

#1


Weird, so all of your changes are committed, but something failed on the remote side of things?

很奇怪,所以你所做的所有更改都已提交,但是在远程方面出现了一些失败?

If that's the case I would try re-deploying the changes using OpenShift's deployment and rollback options. Basically, use rhc deployment list -a <app> to get a list of recent deployment sha1's, use rhc deployment show <deployment_id> -a <app> to view the details of that deployment (optional), and then use rhc deploy <deployment_id> -a <app> to re-deploy the deployment that failed.

如果是这种情况,我会尝试使用OpenShift的部署和回滚选项重新部署更改。基本上,使用rhc部署列表-a 获取最近部署sha1的列表,使用rhc部署show -a 查看该部署的详细信息(可选),然后使用rhc deploy -a 重新部署失败的部署。

$ rhc deployment list -a <app>
$ rhc deployment show <deployment_id> -a <app>
$ rhc deploy <deployment_id> -a <app>

Check out option #2 for full details on how this works.

查看选项#2,了解有关其工作原理的完整详细信息。

#2


My problem was that I was not pushing to git correctly, I was push using the command git push origin master when I was suppose to use just git push

我的问题是我没有正确地推动git,当我假设使用git push时,我正在使用命令git push origin master

example:

git init
git add .
git commit -m "message"
git push

#1


Weird, so all of your changes are committed, but something failed on the remote side of things?

很奇怪,所以你所做的所有更改都已提交,但是在远程方面出现了一些失败?

If that's the case I would try re-deploying the changes using OpenShift's deployment and rollback options. Basically, use rhc deployment list -a <app> to get a list of recent deployment sha1's, use rhc deployment show <deployment_id> -a <app> to view the details of that deployment (optional), and then use rhc deploy <deployment_id> -a <app> to re-deploy the deployment that failed.

如果是这种情况,我会尝试使用OpenShift的部署和回滚选项重新部署更改。基本上,使用rhc部署列表-a 获取最近部署sha1的列表,使用rhc部署show -a 查看该部署的详细信息(可选),然后使用rhc deploy -a 重新部署失败的部署。

$ rhc deployment list -a <app>
$ rhc deployment show <deployment_id> -a <app>
$ rhc deploy <deployment_id> -a <app>

Check out option #2 for full details on how this works.

查看选项#2,了解有关其工作原理的完整详细信息。

#2


My problem was that I was not pushing to git correctly, I was push using the command git push origin master when I was suppose to use just git push

我的问题是我没有正确地推动git,当我假设使用git push时,我正在使用命令git push origin master

example:

git init
git add .
git commit -m "message"
git push