Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate issues with greenkeeper bot #377

Closed
lpinca opened this issue Nov 24, 2015 · 10 comments
Closed

Investigate issues with greenkeeper bot #377

lpinca opened this issue Nov 24, 2015 · 10 comments

Comments

@lpinca
Copy link
Member

lpinca commented Nov 24, 2015

@phillipj has already created this issue greenkeeperio/greenkeeper#68.

If anyone has a clue on why the bot is not working, please share.

This is the list of dependencies to update:

Package              Current  Wanted  Latest  Location
chokidar               1.2.0   1.2.0   1.3.0  nodejs.org
handlebars             4.0.4   4.0.4   4.0.5  nodejs.org
metalsmith-metadata    0.0.2   0.0.2   0.0.3  nodejs.org
nock                  2.18.2  2.18.2   3.3.0  nodejs.org
node-version-data      1.0.0   1.0.0   1.0.1  nodejs.org
semver                 5.0.3   5.0.3   5.1.0  nodejs.org
@lpinca lpinca added the deps label Nov 24, 2015
@phillipj
Copy link
Member

Just noticed there's an error on our side of the greenkeeper webhook. It says it got a 400 status last time it tried to contact greenkeeper. I'll try to sync and/or re-enable greenkeeper as soon as I've got the time.

@christophwitzko
Copy link

Hi @lpinca,
Hi @phillipj,

renaming the repository from new.nodejs.org to nodejs.org might caused the problem.
You can fix that issue by running greenkeeper sync.

Have a great day,
Christoph

@phillipj
Copy link
Member

Thanks for answering @christophwitzko!

Just tried $ greenkeeper sync but it didn't have any effect as far as I can see, the webhook link in this repo's settings are still in a bad state. Also tried $ greenkeeper enable which ended in this message:

→ greenkeeper enable
🌴  info enable The GitHub slug is: nodejs/nodejs.org
🌴  ERR! enable Couldn’t enable a project with this slug.
🌴  ERR! enable If you want to try your free private repo make sure to grant the necessary rights by running $ greenkeeper login --force --private
🌴  ERR! enable You have to have a plan for more than one private repo. To verify run $ greenkeeper whoami
🌴  ERR! enable If you have just recently created this repo try running $ greenkeeper sync
🌴  ERR! enable You need admin access to a repo to enable it.
🌴  ERR! enable If you think this error really shouldn’t appear let us look into it with $ greenkeeper support

Do you know if greenkeeper requires private access to the nodejs github organization? If so we're in bad luck, because we dont allow that kind of permission to any third-party app.

@christophwitzko
Copy link

Hey @phillipj,

thanks for trying. No, Greenkeeper does not require private access. At the moment it looks like Greenkeeper has even no public access to the nodejs organization from your account. Can you revoke access for Greenkeeper application here, then run greenkeeper login --force and grant access to the nodejs organization.

Thank you for your patience,
Christoph

@phillipj
Copy link
Member

@christophwitzko I revoked it, and logged in again as you described. When looking at the greenkeeper settings, the only option I have next to the nodejs org is "request access". Pressing that button warns me it will request org owners for private access. No point going further that way, as nodejs org owners won't allow that anyway..

@mikeal
Copy link
Contributor

mikeal commented Nov 25, 2015

Ya, we need to configure the repo with a push url, we can't grant org wide priviledges to apps.

@stevemao
Copy link
Contributor

Since we've disabled third-party app integrations, we can't use greenkeeper any more :( should we close this issue?

@mikeal
Copy link
Contributor

mikeal commented Feb 26, 2016

I just got a ping from @janl letting me know that they have a greenkeeper enterprise that might work for us on this. I'll work with Jan and the build team to get something in place.

@fhemberger
Copy link
Contributor

@mikeal @janl Any news on this? Or can this issue be closed?

@lpinca lpinca closed this as completed Oct 2, 2017
@janl
Copy link

janl commented Oct 24, 2017

sorry for letting this drop. We’re still happy to help. GK2 uses GH Apps (neé Integrations) and is available in the Marketplace with an Open Source plan. Feel free to give that a spin and let me know if anything doesn't work for you. — if you need support for private repos, give me a shout.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants