Git-updater: Push to deploy broken with 6.3.0

Created on 28 Apr 2017  路  26Comments  路  Source: afragen/git-updater

With the latest version of GitHub Updater (6.3), push to deploy doesn't work anymore.
I haven't touched the settings.

After I restored GitHub Updater 6.2.2, push to deploy worked again.

Note: tested with Bitbucket and a private repository

bug fixed

All 26 comments

Are you referring to using a webhook?

Yes

Did your API key change or did you change how the webhook was setup? Does the Webhook section in Bitbucket display the reponse?

I personally use the feature to update GHU on my test site with each commit to develop. So I know it's working here. I did find that a couple of other webhooks I had set up previously were failing because of a bad API key.

I need to make more tests, but I can't do them today. What I remember is that there was an error during the upgrade of GitHub Updater, but the version number was 6.3.0 after the upgrade.
I'll reinstall all the files manually, test again and keep you informed.

The API key wasn't changed. Once I reinstalled version 6.2.2, it worked as before.

I just did a new test on another project. The upgrade of GitHub Updater was successful, but when I pushed a commit, it wasn't deployed.

Here's the response body:

{
  "messages": [
    "Downloading update from <span class=\"code\">-- URL REMOVED --</span>&#8230;",
    "Unpacking the update&#8230;",
    "The package could not be installed. PCLZIP_ERR_BAD_FORMAT (-10) : Unable to find End of Central Dir Record signature"
  ],
  "response": {
    "hash": "c5e022d4e60470b7d50585e484e25a264caa2afa",
    "branch": "develop",
    "json_error": "No error"
  },
  "error": true
}

That error is an authentication error. You might want to re-enter your password and test to see if it's correct.

The only thing I haven't tested is using your email as a username.

It think I know what it is. I changed the addition of the Basic Auth header to a new class and I'm guessing something isn't adding it during the REST update.

I'll look into and have a fix soon. Thanks for the report.

Can you switch to the develop branch of GitHub Updater and test again? I think I found the issue https://github.com/afragen/github-updater/commit/a96e004eb3dc6a45cac553650116d376bf06708d

I get the same error after having switch to the develop branch.

Yeah, I just tried locally. Stay tuned.

I believe it's now fixed. I had to account for a different $_REQUEST format in class Basic_Auth_Loader. https://github.com/afragen/github-updater/commit/542ac4bd4ddc7e29707c330b091de4dafc6ab9c4

And still works elsewhere 馃挴

Reload the develop branch to test.

Tested with version 6.3.0.3: it works.
Thank you for the fix.

I'll let you close the issue once you push the hot fix.

I have noticed it doesn't work again with 6.3.3
A bug was introduced between 6.3.2 and 6.3.3

Can you try testing the develop branch?

in develop branch still not working.

Some updates from master branch: (testing with bitbucket)

  1. BitBucket's webhooks do not work. As it's stated in this issue
  2. However, in plugin screen, clicking update triger (link) plugin from bitbucket is updated as should

I hope this help more

Can you tell me what the response from the webhook is?

HTTP status: 500

Body

{
  "messages": [
    "Tiek lejupiel膩d膿ts jaunin膩jums no <span class=\"code\">https://bitbucket.org/simplemediacode/********/get/*******02d*******.zip</span>&#8230;",
    "Tiek izpakots jaunin膩jums&#8230;",
    "Pakotni nevar膿ja instal膿t. PCLZIP_ERR_BAD_FORMAT (-10) : Unable to find End of Central Dir Record signature"
  ],
  "response": {
    "hash": "XXXXXY*******",
    "branch": "master",
    "json_error": "No error"
  },
  "error": true
}

_Translation_:
Tiek lejupiel膩d膿ts jaunin膩jums no = Downloading update from
Tiek izpakots jaunin膩jums = unpacking update
Pakotni nevar膿ja instal膿t = Can't install package

******* and XXXXXY******* are hashes

serverside everything works as should.

Please test with develop branch. I think I've fixed it.

Look like update work, but
in BitBucket I receive Request status: TIMEOUT. By visiting webhook's URI for plugin update (in my case), header response status is 200;

No errors in logfile of server.

The timeout sounds like an intermittent issue with Bitbucket.

I works again with develop branch. Thanks for the fix.

Thanks for your help. Releasing fix now.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

alexjose picture alexjose  路  14Comments

NoWorries picture NoWorries  路  5Comments

picasso picture picasso  路  9Comments

alexclassroom picture alexclassroom  路  5Comments

klihelp picture klihelp  路  4Comments