Can't create a Github Release
So I'm having some problems creating a github release.
I get this error Error creating GitHub release: Error reading repository 'kellyelton/OCTGN' releases: 401 - Unauthorized
I created a personal access token to fill into `GitHub authentication token` and I think that's the problem. On your site you say to use https://github.com/settings/applications , problem is the UI doesn't let you create those anymore on that page.
Not really sure where to go from here.
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Feodor Fitsner on 18 May, 2015 06:09 PM
OK, I see. GitHub was redesigned a little bit. Personal access token could be added here: https://github.com/settings/tokens
Will update docs shortly.
2 Posted by its.the.doc on 18 May, 2015 06:13 PM
Alright thanks. I figured that's what I need so I just used that instead, but the problem is that give me a access denied. I use the same key and your instructions to push back to github once the build is complete, and that works.
The one thing is, I'm trying to push the release to an organization repo(that I'm the owner of), and at the end when I push back to github I push back to my fork.
I searched high and low but couldn't find any information reguarding personal access tokens and api calls to organization repo's...I'd assume since I have full access to the repo I shouldn't have any problem, but that doesn't seem to be the case. Oh also, what it could be, is I made it a secret variable, and then put $(access_code) in that box...is it possible that that box doesn't properly read that?
Support Staff 3 Posted by Feodor Fitsner on 18 May, 2015 06:19 PM
Well,
$(access_code)should work unless it's not Pull Request where encrypted variables don't work. Anyway, you can try explicitly specifying access code in that box.To make sure you can create release in that repo you can use Poster or Fiddler to call this API: https://developer.github.com/v3/repos/releases/#create-a-release with
Authorization: token <your-personal-access-token>header added.4 Posted by its.the.doc on 18 May, 2015 06:28 PM
Alright, I tried that and I got access denied again. I even gave the token access to everything I could and it didn't work. I opened a support ticket with github and I'll post back here with what I find.
Support Staff 5 Posted by Feodor Fitsner on 18 May, 2015 06:31 PM
Have you tried calling GitHub API directly?
6 Posted by its.the.doc on 18 May, 2015 06:36 PM
OK nevermind, using the api key and fiddler I was able to make it work. I just typo'd part of the header.
7 Posted by its.the.doc on 18 May, 2015 07:03 PM
Alright, so I generated a new access token, and that doesn't seem to throw me a 401, it does however take a really long time and then it throws some general error
```Deploying using GitHub provider
Creating "1.1.178.0" release for repository "kellyelton/OCTGN" tag "1.1.178.0" commit "6b1c8527cb946c5223d532ead63ae6d2bb82944f"...OK
Uploading "OCTGN-Setup-3.1.170.0.exe" to release assets...An error occurred while sending the request.```
8 Posted by its.the.doc on 18 May, 2015 07:08 PM
Alright(sorry if you can see all this and I'm just spamming you) but I tried again, and again it took a really long time, and return this error
https://ci.appveyor.com/project/KellyElton/octgn/build/1.1.180.0#L3061
"A task was canceled"
9 Posted by its.the.doc on 18 May, 2015 07:10 PM
Also I just noticed that it's not correctly reading the version number.
At the very beginning(in the install script) I use the API to change the version number, and I also set the environmental variable of the version number...yet in the github release deployment deal, if I don't change anything, it defaults to the version number that it starts with before I change anything.
Support Staff 10 Posted by Feodor Fitsner on 18 May, 2015 07:13 PM
How large is that file?
11 Posted by its.the.doc on 18 May, 2015 07:14 PM
Looks like 10mb
Support Staff 12 Posted by Feodor Fitsner on 18 May, 2015 07:17 PM
Hm, and it fails like in 1 second after release created... interesting
13 Posted by its.the.doc on 18 May, 2015 07:21 PM
Well not 1 second...the upload seems to take like minutes and minutes, probably like 5 or 6 or something, then it fails.
Support Staff 14 Posted by Feodor Fitsner on 18 May, 2015 07:26 PM
OK, I see. It fails on 10th minute as we have 10 minutes timeout while uploading a file. Didn't expected it could take so long to push artifact to release.
15 Posted by its.the.doc on 18 May, 2015 07:30 PM
Ok so I did it on their user interface, and it took 10 seconds. I wonder why that is.
16 Posted by its.the.doc on 18 May, 2015 08:13 PM
Sorry not trying to be a pest here, but I was just seeing if you were looking into this.
Support Staff 17 Posted by Feodor Fitsner on 18 May, 2015 09:08 PM
Need to further investigate that. Uploading asset through API is not the same as on UI: https://developer.github.com/v3/repos/releases/#upload-a-release-asset
18 Posted by its.the.doc on 18 May, 2015 09:56 PM
Ok. Well it looks like it's actually working quickly now. Maybe github was just having issues. I also noticed some page loads were taking a long time when I was doing other stuff.
As a side note, I noticed that I changed the build version number in the Install script portion, and doing assembly patching with {version} still tried to use the initial version number. I'm not sure if this is a bug or intended, though I worked around it anyways.
Thanks again for the help.
its.the.doc closed this discussion on 18 May, 2015 09:56 PM.
Feodor Fitsner re-opened this discussion on 18 May, 2015 10:14 PM
Support Staff 19 Posted by Feodor Fitsner on 18 May, 2015 10:14 PM
Patching with version updated is supposed to work: https://github.com/appveyor/ci/issues/263#issuecomment-101526825
I've just made a simple test: https://ci.appveyor.com/project/FeodorFitsner/simple-console/build/...
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:56 AM.