Authors CurseForge

I tagget last release of GarrisonCommander (2.5.14)

It appears in curseforge as Type release and  status new

I noticed that it's the only one in this status (the other ones are approved) and also it has no checkbox so I no clue on how I could approve it (if approving is necessary, which would be a pain, anyway, tagging should be enough.

In curse it says addon was updated but the release offered for download is still 2.15.3

Sincerely, the old packager was slow and sometimes got stuck, but at least you could have an insight on its attivity from status page.

Now we are blind.

Also removing ssh access broke eclipse egit.

Really, while I understand the need to make new interface for general sites, this one is for developer and it was really better in the old way. 

Torhal: Thanks, I did but it's very minimal... just "requested, processing, processed, completed".

There is no clue at all on what went wrong.

I didnt retag the project to nhot make things worst but I just fixed a nasty bug and really would like to update the addon. Should I make a new tag? Sometimes doing this with the old packager restarted the queue and bit tags were processed

I dont want to create alpha files, I am desperately trying to release a new version.
This is the build: https://wow.curseforge.com/dashboard/builds/4155

In files list version 2.15.4a is tagged R for release.

I also tried manually uploading the generate zip file

Guys, really, I know this is a free service (actually, you payme with the reward program :) ) but if you just have a look here

https://wow.curseforge.com/projects/garrisoncommander/files

and here

https://mods.curse.com/addons/wow/garrisoncommander

you will clearly see the issue

I have released two new versions (2.15.4 and 2.15.4a) both clearly tagged as release, but at mods.curse.com the proposed download is still 2.15.3

Now tagged again 2.15.4.1. Again package is created but not pushed to curse.

And again:

changed settings to "package all" (not what I wanted, but just incase)

committed revision 0891255d7a264317d7cfaf8feddab835faedc56b

verified that an alpha zip file was created (GarrisonCommander-0891255-alpha.zip)

tagged as 2.15.5

verified that a release zip was created GarrisonCommander-2.15.5-zip

Curse site says addon was updated 1 minute ago but still proposes 2.15.3 which is almost one month old

I note that while all my old file has a "Approved" column and a checkbox in the rightmost column, everythihng generated  after migration has a "New" column and no checkbox in the rightmost column.

Was some kind of approval added to the process? I cant find any clue

Moved git to bitbucket, set up hooks.

Now is not even building the zip

Seriously guys "if aint broken aint fix it" is the golden rule

Is there at least a way to directly upload a file to curse???

Response from https://wildstar.curseforge.com/api/projects/86760/package?token=xxxxxxxxxxxxxxxxxxxxx

• HTTP status: 400
• Elapsed time: 146ms
• Request time: <time title="2016-11-23T23:05:48.435370Z" data-reactid=".0.0.0.2.1.1.1:$Attempt 4.0.1.$Request time.2.0">a few seconds ago</time> (Thursday, November 24th 2016, 12:05:48 am)

Answer:

{
  "errorCode": 1015,
  "errorMessage": "Invalid project ID."
}
Obviously, I double checked the project ID

Same issue for https://wow.curseforge.com/projects/itemleveldisplay

Zip created, nothing pushed to curse

Well, I know that "right now" is not to be taken literally but 8 hours later still:

Response from https://wildstar.curseforge.com/api/projects/86760/package?token=editedout

• HTTP status: 400
• Elapsed time: 214ms
• Request time: <time title="2016-11-24T09:44:56.558720Z" data-reactid=".0.0.0.2.1.1.0.1.$Request time.2.0">a few seconds ago</time> (Thursday, November 24th 2016, 10:44:56 am)

Headers

Content-Length	55
X-AspNet-Version	4.0.30319
Set-Cookie	__cfduid=dc4c4543d71925a381eacf593865cde4b1479980696; expires=Fri, 24-Nov-17 09:44:56 GMT; path=/; domain=.curseforge.com; HttpOnly
Server	cloudflare-nginx
Connection	keep-alive
X-UA-Compatible	IE=edge,chrome=1
X-AspNetMvc-Version	1.1
Cache-Control	private
Date	Thu, 24 Nov 2016 09:44:56 GMT
CF-RAY	306becd8bce7569f-IAD
Content-Type	application/json; charset=utf-8
X-Frame-Options	SAMEORIGIN
X-Cobalt-Cache	Uncached

Body

{
  "errorCode": 1015,
  "errorMessage": "Invalid project ID."
}

Request

• Attempt type: Initial attempt

Headers

X-Request-UUID	d2c888ce-bbdc-4367-a338-639b457c00ee
X-Event-Key	repo:push
User-Agent	Bitbucket-Webhooks/2.0
X-Attempt-Number	1
X-Hook-UUID	17bb9cb4-310e-4dcc-941f-92988cd29c9d
Content-Type	application/json

aaaand a new status in my "files" listing for both ItemLevelDisplay (zip file generated by curse after tagging repository) and GarrisonCommander (zip file manually uploaded):

"Under review" (waited 30 minutes in this status before posting)

Looks fixed now, good job guys!

Now, some informations about the "Under Review" / "Approved" transition could be useful, but it's not an urgent matter

@alar: change "wildstar" to "wow" on the webhook address.... their example is for the wrong game :)

Bonk me! Wildstar was a reasonable generic like .* in a regexp :)

Thank you mate

No problem, I made the same mistake myself... so easy to just skim over :)