Quote:
|
Classic Release
How do I make and additional classic release?
Can I just add add asecond script line like this?: script: curl -s https://raw.githubusercontent.com/Bi...ter/release.sh | bash script: curl -s https://raw.githubusercontent.com/Bi...ter/release.sh -g 1.13.3 | bash Together with the tags for the toc: #@retail@ ## Interface: 80200 #@end-retail@ #@non-retail@ # ## Interface: 11303 #@end-non-retail@ |
Quote:
For the script part I'm unsure, I stopped using Travis. |
What are you using now?
|
Is there a guide for github actions? (preferably not from moorea)
|
Quote:
|
Quote:
I'm not sure what I'm even doing but the workflow seemed to work, it packaged a tag for me https://github.com/ketho-wow/KethoIn...runs/440568923 |
Quote:
A basic non-docker workflow would be something like this: https://gist.github.com/nebularg/7b2...de591023cca245 As another example, here is the workflow I use for PitBull4: https://github.com/nebularg/PitBull4...lows/build.yml |
Quote:
Code:
script: Quote:
|
Quote:
Oh, thanks! I changed it to this workflow now It did throw an error when uploading a file to GitHub. Something about the file already existing, although I don't see the zip in my release assets :confused: edit: must be just a mishap, it's working on my other projects Code:
Creating GitHub release: https://github.com/ketho-wow/VendorPrice/releases/tag/1.3.1 |
What a great guide! Thanks!
Updating these links in the original post would make it even more convenient: https://authors.curseforge.com/knowledge-base/world-of-warcraft/527-preparing-the-packagemeta-file -> https://authors.curseforge.com/knowledge-base/projects/527-preparing-the-packagemeta-file https://authors.curseforge.com/knowledge-base/world-of-warcraft/532-repository-keyword-substitutions -> https://authors.curseforge.com/knowledge-base/projects/532-repository-keyword-substitutions |
DISCLAIMER
This guide has been deprecated in favour of GitHub Actions, as it's more integrated and (honestly) easier to set up. A full guide is provided on the wiki for the packager itself. Direct link: https://github.com/BigWigsMods/packa...tions-workflow |
Quote:
|
Quote:
2. Store the token as a secret for your project on GitHub, name it WOWI_API_TOKEN 3. Define WOWI_API_TOKEN as an environment variable in the workflow How to get a WoWInterface token is documented in the packager readme, how to add GitHub secrets is documented in the wiki page for the action, and how to add it as an environment variable in the workflow is also documented there. |
Ignore this. I really should look at the dates. :p
|
I'm having issues setting up my GitHub workflow and was hoping to get some help.
https://github.com/niketa-wow/guildb...thub/workflows What I'm trying to accomplish: 1. Tags created from my development branch should remove the WoWI addon id as they will be alpha/beta releases only, which WoWI doesn't support. 2. Tags created from my stable branch should upload to both Curse and WoWI per usual. 3. Only new tags should be created. Problems I'm having: In the example I linked, I created a tag "GuildBankSnapshots-v2.0.4". I typically tag "AddonName-v0.0.0-beta", etc. 1. Builds are being tagged as alphas when they should be releases. 2. Possibly because of the above problem, nothing is being uploaded to WoWI. The API token is set up for the repo, so that's not the problem. 3. Uploads are being named with a random string at the end (for the commit or something, idk; I'm still a relative noob to git). 4. Pushing commits after creating a tag triggers builds again for the same tag. I tagged and pushed v2.0.4 and then made a small change to the workflow file and committed, which triggered the action to upload to Curse AGAIN for the same tag/file. I wasn't really having issues like this with travis-ci, so I'm sure it's something about the "on" part of my Github actions and I can't quite figure it out. Thanks! (This particular addon, I need to change it up again and remove classic as it's not relevant for it. Copy and pasted from another addon I primarily work on and forgot to take that off. But alas, I'm afraid to make the change again and have to go back and manually delete files from Curse again. Been doing that all night.) |
Looks like most of your problem is your tags line.
For your "stable" builds, try something like: Code:
on: Code:
on: You don't need your add-on's name in tags. The packager does that and it's kind of redundant. So keep them simple, like "v2.0.4" or "v2.0.4-beta". If you must do it, make sure you include it in your tag lines for your workflows. The tag lines match the name of tags (regex-ish), so you'd do something like: Code:
- 'GuildBankSnapshots-*.*.*' |
Quote:
Just for educational reasons, could you explain why the previous version I had may have behaved in the way they did? Such as why it was rerunning on old tags and releasing everything as an alpha? Also, should I have my workflows only on my stable branch or should I have it on my development branch too? I'm thinking just stable because I think it was double uploading when I had it on both, but I want to be sure I understand it right. Thanks! |
Quote:
Quote:
If you want it more refined, you could add back in the branch filtering that you had previously. Alternatively, if your commits and tags are exclusive to their respective branch (ie, you only push alpha/beta to the development branch), you could simply remove the stable workflow from the development branch and remove the development workflow from the stable branch. |
I'm having some more issues with my configuration for Github actions.
It seemed to be working fine when I released stable versions, but whenever I try to release an alpha, the packager says "Found future tag "v3.0-alpha3", not packaging." I can't figure out how to make it actually package and release like it's supposed to and it's been getting rather frustrating. Here is the config file. I had to add the branch name to the clone project step because whenever I left that out, it would just repackage and release my latest release version (v2.1.5). However, after I changed this it recognized the alpha version (v3.0-alpha3), but gave the above error. I tried messing around with the on push tags but it was a no go with anything I tried. |
All times are GMT -6. The time now is 07:29 AM. |
vBulletin © 2024, Jelsoft Enterprises Ltd
© 2004 - 2022 MMOUI