Pushing gh-pages fails every other attempt

This discussion is public.

patcherton.fixesthings's Avatar

patcherton.fixesthings

24 Apr, 2023 06:10 PM

At some point between 2023-04-05 and 2023-04-19, my automatic builds started failing on the first try because of errors when pushing to gh-pages. Running the build again always succeeds, but why is it failing in the first place? It only started happening within the past few weeks.

The given error message is

git : remote: Resolving deltas:   0% (0/3)
At line:14 char:1 + git push -q origin gh-pages + ~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (remote: Resolvi...% (0/3) :String) [], RemoteException + FullyQualifiedErrorId : NativeCommandError


remote: Resolving deltas: 33% (1/3)
remote: Resolving deltas: 66% (2/3)
remote: Resolving deltas: 100% (3/3)
remote: Resolving deltas: 100% (3/3), completed with 3 local objects.
Command executed with exception: remote: Resolving deltas: 100% (3/3), completed with 3 local objects.

Compare...

Failure: https://ci.appveyor.com/project/fiendish/aardwolfclientpackage/buil...
Success: https://ci.appveyor.com/project/fiendish/aardwolfclientpackage/buil...

  1. Support Staff 1 Feodor Fitsner's Avatar Feodor Fitsner on 24 Apr, 2023 06:26 PM

    It's because the last git push command writes some output to StdErr which is treated as an exception by built-in PowerShell host in build agent.

    Try moving that command out of that PS command into a separate, like:

    before_deploy:
    - ps: >-
        $env:PACKAGE_VERSION=(Get-Content MUSHclient\AardwolfPackageChanges.txt)[2].split()[0]
    ...
        git add index.html 2>&1 | write-host
        git add unzip_upgrading.html 2>&1 | write-host
        git commit -q -m "automatic rev update $env:PACKAGE_VERSION"
    - git push -q origin gh-pages
    
  2. 2 patcherton.fixesthings's Avatar patcherton.fixesthings on 28 Apr, 2023 05:23 PM

    Any idea why it only started happening recently? I've been using the same config for years.

  3. Support Staff 3 Feodor Fitsner's Avatar Feodor Fitsner on 28 Apr, 2023 05:25 PM

    My guess would be Git upgraded in the image multiple times. Could be changes in output of recent Git versions.

  4. Feodor Fitsner closed this discussion on 28 Jun, 2023 09:02 PM.

Comments are currently closed for this discussion. You can start a new one.