Thanks, Nevcariel. Please let me know if there is anything I can do to get Grid to build properly. I have an e-mail in to Phanx to ask if he would mind if I try deleting all current tags and create a new one to see if that would fix the build issue. Not an ideal option if it can be fixed on the Curse side.
FWIW, I occasionally run into crazy tag problems with one of my larger addons. I'm using Mercurial, and as a workaround I occasionally move tag entries out of .hgtags and into .hg/localtags (which isn't pushed to the server).
It's a horrible abuse of tags, but it means that when the packager goes bonkers and begins repackaging *every* tag as "the latest", it's limited to a small handful and not all of project history.
Maybe Git has something similar you could temporarily abuse?
I've deleted all of the existing tags as mentioned in this thread and pushed a new tag; I don't know if this will actually solve anything, though.
Edit: It looks like pushing the new tag caused all of the existing files to be refreshed. I have no idea how that's possible when there aren't any tags to package, though. Can't we just remove all files and all repository data from the project, and then I create a new repository and push to it without any of the historical baggage that's screwing up the packager?
As Phanx said above, he tried deleting all tags and rebuilding. The issue still occured with only one tag. It seems like sometimes the Curse packager does the previous build instead of the current build and that looks like what happened as it didn't build the current tag (220.127.116.11-beta) he added but all the old tags.
I'd like to try another build with the new tag (I can delete it and create it or create a new tag) now that there is only one tag. Someone on the Curse side disabled packaging on Grid (was neither Phanx nor I).
I don't want to turn packaging back on and get in trouble for overloading the packager if removing the tags didn't fix the issue.
Or can someone on the Curse side manually launch another package of the 18.104.22.168-beta tag and see if the issue is at least somewhat resolved?
So far that is the only version of Grid built on Curse that actually works. I changed it from alpha to release so that people will start downloading a working version with Curse client (although not current).
I had this same issue with SpartanUI I ended up finding a issue with the conversion process. So far i have only made 1 tag since cleaning up i will do a few tests and see what i can find out since i know someone else is having the same headaches as me.
TLDR: I had to delete all my tags. And you need to ensure Curse tags get deleted not just your local ones.
Info for other people who find this:
If you open your Git Repo with SourceTree Do your tags appear as dead-end branches?
Below is a screenshot of my oUF repo, all the lines on the left are all the branches, click on Branches to get this view. http://i.imgur.com/EEaIORy.png
Now it sounds and looks wierd, they are not branches since they are not labeled as a branch, sourcetree will show you only have 1 branch. Even git command lines will return that there is only 1 branch. Something in SourceTree is able to see them as a "partial" branch and I think the Curse Packager is seeing it as well. If you delete the tag the commit will no longer appear as a branch and will then fall in line with the rest of the main repo's branch. Once all tags are deleted new tags will function as intended.
Sorry for double post but. I was able to run the tests after cleaning the repo of all old tags new tags are working:
So to test i added a empty text file and did a commit, i got an alpha zip
-Commit A - <Date>.zip
-Commit A - Tag Added - <Tag>.zip
-Commit B - <Commit A Tag>-1-<Commit ID>.zip
-Commit C - <Commit A Tag>-2-<Commit ID>.zip http://imgur.com/eSeaGfo.png
The Commit that is tagged 4.1.1-Release never had a zip made until AFTER the following commit occurred due to packager being a bit overloaded yesterday, i think we can count that one as a rare occurrence.
I am not seeing duplicates anymore for my Repo after deleting of all old tags, if someone on the GRID team has a backup of their repo pre-tag deletion i would love to see if they have the "dead-end branches"
Wutname1, I am glad deleting tags worked for you, but it didn't work for Grid. Someone enabled packaging on Grid again and I took that as permission to try again. The issue is still there even with only a single tag in the repository. I don't know where the packager is getting all the tags to build from. Obviously it has cached them somewhere.
I deleted the previous tag and created a new one (only a single tag in the repo):
Ya, something is definitely cached. You could try pushing a blank repo or setting the repo back to SVN then back to GIT in a effort to wipe what ever is sitting on wowace. I would then try a test push that would generate a lone alpha build before re-pushing the real repo with cleaned tags.
Also there looks to be some log differences based on curseforge or wowace project (I know in the backend they are said to be the same) but looking at packager status there is alot more information given on Curseforge, SUIGRID on curseforge i can see what repo is getting pulled into "media/cf-repositories/packager/zip/wow/<zip name>" and i can also see Tags that are to be handled. I dont think this will find the issue since it only affects nolib builds but hopefully someone at curse might get an idea based on the finding.
Phanx would have to be the one to change the repo. I would be nervous about changing it to SVN and back to Git as that could just make the situation worse.
I have a bunch of fixes for Grid I would love to release, but without being able to build or upload zip files I am not sure what the solution is. I would really appreciate an update from the Curse folks on this issue.
I just did a commit/push with no tags, but that apparently triggered another build even though alpha builds were not enabled. The Curse packager is fine with my other addons; but it is totally screwed up with Grid.
Someone did another build this morning other than me. Phanx has packaging disabled, so I doubt it was him. If it was someone on the Curse side, please at least delete the oldest version with the actual .zip file (non -nolib) version if you do a build so that people don't download a WoW 3.0.9 version of Grid.
1.30000.2009011501 Release Normal 1 hour ago 3.0.9 Grid-1.30000.2009011501.zip 6,223
Over 6,000 people downloaded invalid old versions before I saw the e-mails about the build and had a chance to delete all the files created by the build an hour ago.
Please leaving packaging off at this point. With the move to Curseforge we can now upload zips manually. Phanx and I are now using a third-party packager that seems to work fine. I uploaded a new 22.214.171.124 version produced by this new packager.