I've setup my project to use GitHub webhooks to package my tagged commits as specified on this page: http://wildstar.curseforge.com/docs/packaging. My question is how long does it usually take for the files to upload on the CurseForge project page? It's been about 20 minutes since I tagged my first release and still nothing.
Just in case it is helpful, my project is here: http://wildstar.curseforge.com/ws-addons/222916-vocalcombat. At the time of this post it's still awaiting initial moderation for approval and I set it up as "experimental". So it would make sense if that was a factor in this. I'm just trying to figure out what to expect at this point and as I move forward.
Apparently, GitHub uses lightweight tags for their releases, and we're looking for actual (annotated) tags. Something I'll look at in the morning, but if you want to get going now keep that in mind.
Thanks for the response Torhal. I've tried it with an annotated tag as well, still a no go. So possibly just a general issue with GitHub hooks?
I'd really recommend not requiring annotated tags. The GitHub webhooks do in fact fire off of the lightweight tags, which should be everything needed to actually let CF know about a new version.
We're pushing out an update tonight that handles lightweight tags; it was actually ready to go about an hour ago, but an unrelated issue pushed it out a bit. I'll post here with an update when it's live.
We're pushing out an update tonight that handles lightweight tags; it was actually ready to go about an hour ago, but an unrelated issue pushed it out a bit. I'll post here with an update when it's live.
So it's still not working for me. Although everything looks good under the 'Recent Deliveries' for my webhook. Could this be related to the fact that my project on CurseForge is still awaiting moderator approval?
No - projects actually don't even show up for the approval queue until a file has been uploaded. When did you push your changes? Your project is also set up to only package on tags.
2: The changelog is all commits between tags. The e-mail address and all of the other information included there is the same information that is readily available via GitHub; in fact, that's where the information is pulled from.
1) It uses the project's URL slug if no package-as is specified. There's no reason to parse the source URL attempting to figure out which portion is the repository name when all that's required is a simple field in the pkgmeta file.
2) It isn't directly visible from GitHub, but anyone who decides to clone your repository will have that information either via their commit GUI or by typing "git log" from a commandline.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I've setup my project to use GitHub webhooks to package my tagged commits as specified on this page: http://wildstar.curseforge.com/docs/packaging. My question is how long does it usually take for the files to upload on the CurseForge project page? It's been about 20 minutes since I tagged my first release and still nothing.
Just in case it is helpful, my project is here: http://wildstar.curseforge.com/ws-addons/222916-vocalcombat. At the time of this post it's still awaiting initial moderation for approval and I set it up as "experimental". So it would make sense if that was a factor in this. I'm just trying to figure out what to expect at this point and as I move forward.
-
View User Profile
-
View Posts
-
Send Message
CurseApparently, GitHub uses lightweight tags for their releases, and we're looking for actual (annotated) tags. Something I'll look at in the morning, but if you want to get going now keep that in mind.
Thanks for the response Torhal. I've tried it with an annotated tag as well, still a no go. So possibly just a general issue with GitHub hooks?
I'd really recommend not requiring annotated tags. The GitHub webhooks do in fact fire off of the lightweight tags, which should be everything needed to actually let CF know about a new version.
:)
-
View User Profile
-
View Posts
-
Send Message
CurseWe're pushing out an update tonight that handles lightweight tags; it was actually ready to go about an hour ago, but an unrelated issue pushed it out a bit. I'll post here with an update when it's live.
Awesome. Thanks Torhal!
-
View User Profile
-
View Posts
-
Send Message
CurseI've just been informed that the deploy won't be happening tonight. I'll update here tomorrow.
Alright thanks for the update. It would be awesome to have this up today, just in time for some weekend dev. ;)
-
View User Profile
-
View Posts
-
Send Message
CurseIt will definitely be up today. I've been assured of that.
-
View User Profile
-
View Posts
-
Send Message
CurseIt's live, now. Go at it!
So it's still not working for me. Although everything looks good under the 'Recent Deliveries' for my webhook. Could this be related to the fact that my project on CurseForge is still awaiting moderator approval?
-
View User Profile
-
View Posts
-
Send Message
CurseNo - projects actually don't even show up for the approval queue until a file has been uploaded. When did you push your changes? Your project is also set up to only package on tags.
Sent full request/response details to you via PM.
Timestamp from the most recent successful response is:
P.S. Really appreciate the ongoing support on this. :)
-
View User Profile
-
View Posts
-
Send Message
CurseYou have packaging disabled on EasyPlant, so that certainly doesn't help. :D
Also, yes - files need manual approval now, no matter their method of creation.
-
View User Profile
-
View Posts
-
Send Message
CurseTry making a new commit then pushing a tag. I was able to get it to package using a test project.
Oh so it's working now?
-
View User Profile
-
View Posts
-
Send Message
CurseThat's the hope...
-
View User Profile
-
View Posts
-
Send Message
CurseWe've worked out some issues; all should be well now.
-
View User Profile
-
View Posts
-
Send Message
Curse1: Read http://wildstar.curseforge.com/docs/packaging - look for "package-as"
2: The changelog is all commits between tags. The e-mail address and all of the other information included there is the same information that is readily available via GitHub; in fact, that's where the information is pulled from.
-
View User Profile
-
View Posts
-
Send Message
Curse1) It uses the project's URL slug if no package-as is specified. There's no reason to parse the source URL attempting to figure out which portion is the repository name when all that's required is a simple field in the pkgmeta file.
2) It isn't directly visible from GitHub, but anyone who decides to clone your repository will have that information either via their commit GUI or by typing "git log" from a commandline.