Fail to deploy to Heroku: Argument list too long - bin/receive_untrusted - heroku

When I try to update my Java app on Heroku it fails with a "Argument list too long - bin/receive_untrusted". This happens before the actual build process starts and it's the only error that I'm getting. Of course it build perfect locally..
Counting objects: 95506, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (28630/28630), done.
Writing objects: 100% (95506/95506), 16.95 MiB | 2.82 MiB/s, done.
Total 95506 (delta 42943), reused 94815 (delta 42643)
remote: Compressing source files... done.
remote: Building source:
remote:
remote: Build stream timed out, reverting to polling...
remote:
remote: Build output:
remote: Argument list too long - bin/receive_untrusted
remote: ! Push rejected to xxxxx.
remote:
To https://git.heroku.com/xxxx.git
! [remote rejected] develop -> master (pre-receive hook declined)
error: failed to push some refs to 'https://git.heroku.com/xxxxx.git'

The only thing that fixed it for me was resetting the Git repo in Heroku and pushing it from scratch, a described in this answer.

Related

Heroku Git error, please try again shortly

I get this error when deploying my Heroku application from the CLI. It always worked fine, even today a moment ago. Now I'm getting this:
$ git push heroku main
Enumerating objects: 46, done.
Counting objects: 100% (46/46), done.
Delta compression using up to 8 threads
Compressing objects: 100% (31/31), done.
Writing objects: 100% (31/31), 4.62 KiB | 788.00 KiB/s, done.
Total 31 (delta 23), reused 0 (delta 0), pack-reused 0
remote: Compressing source files... done.
remote: Building source:
remote:
remote: ! Heroku Git error, please try again shortly.
remote: ! See http://status.heroku.com for current Heroku platform status.
remote: ! If the problem persists, please open a ticket
remote: ! on https://help.heroku.com/tickets/new
remote: ! and provide the Request ID dee02a42-c0d2-4740-b9f3-cbfb58c7d95f
remote:
To https://git.heroku.com/vaquita-escolar.git
! [remote rejected] main -> main (pre-receive hook declined)
error: failed to push some refs to 'https://git.heroku.com/vaquita-escolar.git'
Advice is appreciated.
It was a temporary Heroku issue. It works now (today).

cant git push heroku master - buildpacks

well simply this is what i am getting;
sa#sa-VPCW11S1E:/opt/hubot/bin$ heroku buildpacks
=== young-everglades-12415 Buildpack URL
heroku/java
sa#sa-VPCW11S1E:/opt/hubot/bin$ sudo git push heroku master
Counting objects: 3, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 2.14 KiB | 0 bytes/s, done.
Total 3 (delta 0), reused 0 (delta 0)
remote: Compressing source files... done.
remote: Building source:
remote:
remote: -----> Failed to detect set buildpack https://codon- buildpacks.s3.amazonaws.com/buildpacks/heroku/java.tgz
remote: More info: https://devcenter.heroku.com/articles/buildpacks#detection-failure
remote:
remote: ! Push failed
remote: Verifying deploy...
remote:
remote: ! Push rejected to young-everglades-12415.
remote:
To https://git.heroku.com/young-everglades-12415.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'https://git.heroku.com/young- everglades-12415.git'
sa#sa-VPCW11S1E:/opt/hubot/bin$
although i did set a buildpack on the app git push failed because no buildpack detected ?
How can i resolve this, and is it actually the right steps towards deploying hubot ?
The heroku build packs still use the detection script to identify the language in use. Since Hubot is not a java project and it looks like you are using the java build pack, I suspect the detection script failed.
To fix this, try removing the buildpack.
% heroku buildpacks:remove heroku/java
After this I would try,
% git push heroku master
(Optional) I believe the rediscloud addon is needed for some scripts. You can add it with,
% heroku addons:create rediscloud
Then watch the logs heroku logs and see what happens.
There is a good deployment guide in hubot/deploying/heroku.md

I have a Git repository. I have cloned the repository,Commited my local changes. When I push my changes to the server it shows error

when i pull the chages from clone, it is reflected in server and vice versa. but when i push it shows error.
Error message:
git.exe push --progress "origin" master:master
Counting objects: 11, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (6/6), done.
Writing objects: 100% (6/6), 474 bytes | 0 bytes/s, done.
Total 6 (delta 3), reused 0 (delta 0)
remote: error: refusing to update checked out branch: refs/heads/master
remote: error: By default, updating the current branch in a non-bare repository
remote: error: is denied, because it will make the index and work tree inconsistent
remote: error: with what you pushed, and will require 'git reset --hard' to match
remote: error: the work tree to HEAD.
remote: error:
remote: error: You can set 'receive.denyCurrentBranch' configuration variable to
remote: error: 'ignore' or 'warn' in the remote repository to allow pushing into
remote: error: its current branch; however, this is not recommended unless you
remote: error: arranged to update its work tree to match what you pushed in some
remote: error: other way.
remote: error:
remote: error: To squelch this message and still keep the default behaviour, set
remote: error: 'receive.denyCurrentBranch' configuration variable to 'refuse'.
To //INCHNLRDFS06/CUB Ebanking$/GIT_Ebank
! [remote rejected] master -> master (branch is currently checked out)
error: failed to push some refs to '//INCHNLRDFS06/CUB Ebanking$/GIT_Ebank'
git did not exit cleanly (exit code 1) (1029 ms # 9/10/2014 6:43:09 PM)
If you are cloning from another user's repository, the origin remote (assuming you're pushing to origin) is linked to that user's repo.
In order to commit and push your changes, you first must fork that user's repo and clone from your fork. Doing so will set up your remote to your repo and you can commit and push as you please.
You can view your remotes in the .git/config file and correct them if you're still having trouble.

Push play2 yeoman app to Heroku

Trying to push play2-yeoman to heroku.
As discussed here , I did the following
heroku create --buildpack https://github.com/47deg/heroku-buildpack-scala.git
I see the following
Creating frozen-springs-5883... done, stack is cedar
BUILDPACK_URL=https://github.com/47deg/heroku-buildpack-scala.git
http://frozen-springs-5883.herokuapp.com/ | git#heroku.com:frozen-springs-5883.git
I looked at the forked buildpack, it uses a variable called ${UI_FILES} , so I added that to heroku config using
heroku config:set UI_FILES=ui
However when I try to push I get the following error message
Initializing repository, done.
Counting objects: 889, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (367/367), done.
Writing objects: 100% (889/889), 1.24 MiB | 2.17 MiB/s, done.
Total 889 (delta 312), reused 845 (delta 294)
-----> Fetching custom git buildpack... done
! Push rejected, no Cedar-supported app detected
To git#heroku.com:frozen-springs-5883.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'git#heroku.com:frozen-springs-5883.git'
According to Heroku's devcenter, you can force heroku to build using the Play 2 buildpack by executing the following command:
heroku config:add BUILDPACK_URL=https://github.com/heroku/heroku-buildpack-scala.git

Deploy Play 2.2.1 to Heroku

I'm not able to deploy a Play 2.2.1 app to heroku. Here is what I see:
Delta compression using up to 4 threads.
Compressing objects: 100% (1056/1056), done.
Writing objects: 100% (1163/1163), 271.55 KiB | 136 KiB/s, done.
Total 1163 (delta 565), reused 0 (delta 0)
-----> Removing .DS_Store files
-----> Fetching custom git buildpack... done
! Push rejected, no Cedar-supported app detected
To git#heroku.com:pacific-chamber-5618.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'git#heroku.com:pacific-chamber-5618.git
Any reasons as to why this should fail?

Resources