Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
This happens because the auth_token that is the appveyor.yml does not have access to create github releases.
I'm not sure this is necessary anyway because it looks like Gerrit automatically creates a github release when a tag is pushed to GitHub.
Jeff Morris do you know if this is the case?
Attachments
| For Gerrit Dashboard: NCBC-1360 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 75125,2 | NCBC-1360: Don’t try to create GitHub release on tag in AppVeyor | master | couchbase-net-client | Status: MERGED | +2 | +1 |
Activity
After discussing with Jeff we are happy to remove the AppVeyor step for creating GitHub releases as Gerrit already creates them when a tag is pushed.
After discussing with Jeff - we are going to stop AppVeyor trying to create the GitHub Release. It looks like Gerrit is already doing this and we have not historically attached the binaries zip to the releases so we are not losing anything.
If we wanted to attach the binaries, we would have to stop Gerrit from creating releases and configure AppVeyor to do it.