jekyll-deploy-action: The deployment occasionally silently fails

It’s happened a couple of times for me already: the jeffreytse/jekyll-deploy-action@v0.4.0 action runs and it gets marked as successful, but doesn’t push the built site to the deployment branch.

Looking at the job logs I see the following:

Deploying to nietaki/nietaki.github.io on branch gh-pages
Deploying to ***github.com/nietaki/nietaki.github.io.git
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint: 
hint: 	git config --global init.defaultBranch <name>
hint: 
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint: 
hint: 	git branch -m <name>
Initialized empty Git repository in /github/workspace/build/.git/
[master (root-commit) b482d39] jekyll build from Action c9750a65641e00149d94784206bb9204a98320d1
 158 files changed, 34502 insertions(+)
 create mode 100644 .nojekyll
 (... many lines here cut"
 create mode 100644 til/index.html
error: RPC failed; curl 55 Send failure: Connection reset by peer
send-pack: unexpected disconnect while reading sideband packet
fatal: the remote end hung up unexpectedly
Everything up-to-date

It doesn’t happen consistently, but only every once in a while, but makes me unable to trust my CI.

I’m not sure what the error…

error: RPC failed; curl 55 Send failure: Connection reset by peer
send-pack: unexpected disconnect while reading sideband packet
fatal: the remote end hung up unexpectedly

…refers to specifically, but regardless, I don’t think it should be failing silently.

My workflow is pretty standard, with barely anything modified from the defaults:

name: Build and Deploy to Github Pages

on:
  push:
    branches:
      - master
  schedule:
    - cron: '30 5 * * *'

jobs:
  build_and_deploy:
    # permissions: write-all
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3

      # Use GitHub Actions' cache to cache dependencies on servers
      - uses: actions/cache@v3
        with:
          path: vendor/bundle
          key: ${{ runner.os }}-gems-${{ hashFiles('**/Gemfile.lock') }}
          restore-keys: |
            ${{ runner.os }}-gems-

      # Use GitHub Deploy Action to build and deploy to Github
      - uses: jeffreytse/jekyll-deploy-action@v0.4.0
        with:
          provider: 'github'
          token: ${{ secrets.GITHUB_TOKEN }} # It's your Personal Access Token(PAT)
          repository: ''             # Default is current repository
          branch: 'gh-pages'         # Default is gh-pages for github provider
          jekyll_src: './'           # Default is root directory
          jekyll_cfg: '_config.yml'  # Default is _config.yml
          jekyll_baseurl: ''         # Default is according to _config.yml
          bundler_ver: '>=0'         # Default is latest bundler version
          cname: 'nietaki.com'                  # Default is to not use a cname
          actor: ''                  # Default is the GITHUB_ACTOR
          pre_build_commands: ''     # Installing additional dependencies (Arch Linux)

Let me know if there are any other details I should provide

About this issue

Original URL
State: closed
Created a year ago
Reactions: 2
Comments: 19 (7 by maintainers)

Commits related to this issue

fix: dev: replace with custom action with Based on this issue: https://github.com/jeffreytse/jekyll-deploy-action/issues/64 The original poster was able to fix the error by applying the git config t... — committed to pgpbpadilla/pgpbpadilla.github.io by pgpbpadilla a year ago
fix: the remote end hung up unexpectedly (#64) When pushing a large amount of data (initial push of a big repository, change with very big file(s)) may require a higher http.postBuffer setting on you... — committed to jeffreytse/jekyll-deploy-action by jeffreytse a year ago
fix: usr: use pre_build_commands hook to change git config as suggested in https://github.com/jeffreytse/jekyll-deploy-action/issues/64#issuecomment-1556498538 — committed to pgpbpadilla/pgpbpadilla.github.io by pgpbpadilla a year ago
Trying to work around deploy issues Based on https://github.com/jeffreytse/jekyll-deploy-action/issues/64 — committed to geoserver/geoserver.github.io by aaime a year ago
Update build-jekyll.yml - https://github.com/jeffreytse/jekyll-deploy-action/issues/64 — committed to perryOnCrack/perryoncrack.github.io by perryOnCrack a year ago

Most upvoted comments

Hi @nietaki, @longavailable, @jtmullen

Thanks for your reporting. Now the issue should be fixed. Please update to the latest version jeffreytse/jekyll-deploy-action@master and try again. : )

Thanks & Regards

jeffreytse on May 22, 2023

Hi @davidalpert @nietaki, @longavailable, @jtmullen

Now the latest version has supported to deploy site via the SSH protocol for better stability comparing with HTTP protocol, here I suggest you to switch to the SSH protocol as saying. : )

Thanks & Regards

jeffreytse on Jul 17, 2023

it seems to me that this discussion is about two separate issues:

the error: RPC failed; curl 55 Send failure: Connection reset by peer git error; and
the step failure is silent

above I see a discussion about the git issue.

is it perhaps worth opening a second issue to discuss the fact that this action can fail silently such that the workflow can report success and you have to read the build log to see that it did not actually succeed?

davidalpert on Jun 18, 2023

I was able to resolve this for my use case by forking the action and adding git configuration to increase the http post buffer size. An optional argument for post buffer size would be a nice improvement.

For the alternative solution, you can use pre_build_commands option as below:

pre_build_commands: git config --global http.version HTTP/1.1; git config --global http.postBuffer 524288000;

jeffreytse on May 22, 2023

I was able to resolve this for my use case by forking the action and adding git configuration to increase the http post buffer size. An optional argument for post buffer size would be a nice improvement.

malachi-constant on May 19, 2023

@longavailable Could you try one more time? And before you try, you need to create a new secret named SSH_PRIVATE_KEY which content is a private key format in your repository Settings > Secrets and Variables > Actions as the following screenshot.

jeffreytse on Jul 17, 2023

Hi @pgpbpadilla, could you try to use action jeffreytse/jekyll-deploy-action@master again?

jeffreytse on May 23, 2023

I see that this may be an issue external to this action: https://github.com/orgs/community/discussions/55820

Of course it would still be better that the action fail in this scenario.

jtmullen on May 19, 2023

Hi @nietaki Could you provide the repo address? So that I can have a further check. : )

jeffreytse on Apr 26, 2023