CircleCI permission denied error

[Phanabani]

Hey @oxyno-zeta!

I'm just about ready to release v2.3.0. The last issue I'm working on, #42, ran into a problem that I need your help for.

I've updated the CircleCI config, but the build failed with the reason: "Permission denied (publickey)". I think you need to generate a new GitHub deploy key. This answer here seems to give a simpler summary of what you need to do.

I'm not 100% sure if this is the issue, but I don't have the permissions to investigate further, so I need your help whenever you're available! Hopefully this will fix the problem and I can finish up. :)

[oxyno-zeta]

Hello,

I removed and added back another key. Tell me if it is working now.

Regards,

Oxyno-zeta

PS : I cannot find your branch on circle, cannot be sure that will work :(

[oxyno-zeta]

After checking deeper, I think the configuration for CircleCI isn't working anymore. Maybe it is time to switch to Github CI. What do you think of this ?

[Phanabani]

@oxyno-zeta I got it to succeed! My branch is named change/update-ci-config btw, not the 2.3.0 branch.

Do you still want to transition to Github CI, or is it okay to remain with Circle?

[oxyno-zeta]

Oh for me it is ok to remain on circle. Was thinking doing it from scratch may be easier on GitHub but I'm ok to stay on Circle if you prefer.

[oxyno-zeta]

Maybe because your release branch is on your fork ? I don't remember if it was accepted to build forks...

[Phanabani]

Hmm, I'm not sure because my branches are on your repo, not my fork. 🤔

I'm going to merge the Circle config update into release/2.3.0, but I'll try implementing the Github CI on another branch to see if it's easier!