WoWInterface

WoWInterface (https://www.wowinterface.com/forums/index.php)
-   Tutorials & Other Helpful Info. (https://www.wowinterface.com/forums/forumdisplay.php?f=12)
-   -   Guide: Automagically package and publish addons (https://www.wowinterface.com/forums/showthread.php?t=55801)

p3lim 10-01-19 09:06 AM

Quote:

Originally Posted by MooreaTv (Post 334060)
You can use Github Actions (just need to signup for it and afaik everyone asking gets immediate access to it) to run the packager with no other dependencies

here is an example:
https://github.com/mooreatv/AuctionD...packaging.yaml

There are plans for something simpler than that ;)

yess 02-01-20 05:19 PM

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:

#@[email protected]
## Interface: 80200
#@[email protected]
#@[email protected]
# ## Interface: 11303
#@[email protected]

p3lim 02-01-20 07:28 PM

Quote:

Originally Posted by yess (Post 335065)
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:

#@[email protected]
## Interface: 80200
#@[email protected]
#@[email protected]
# ## Interface: 11303
#@[email protected]

The TOC file looks right, but remove the "# " at the front of 11303.
For the script part I'm unsure, I stopped using Travis.

yess 02-01-20 10:05 PM

What are you using now?

Ketho 02-02-20 05:18 AM

Is there a guide for github actions? (preferably not from moorea)

p3lim 02-10-20 05:04 PM

Quote:

Originally Posted by Ketho (Post 335068)
Is there a guide for github actions? (preferably not from moorea)

We had plans of supporting actions directly with the packager repo (see https://github.com/BigWigsMods/packager/pull/44), but we hit some snags with the implementation (both actions and "packages") by GitHub. Don't know if that's been resolved or not now, feel free to test it.

Ketho 02-12-20 02:23 AM

Quote:

Originally Posted by p3lim (Post 335106)
Don't know if that's been resolved or not now, feel free to test it.


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

nebula 02-14-20 05:49 PM

Quote:

Originally Posted by Ketho (Post 335124)
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

You only need that second step (the block after "# run release.sh with arguments") for it to work :p

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

nebula 02-14-20 06:00 PM

Quote:

Originally Posted by yess (Post 335065)
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

To add another script entry you need to make it a list and to build classic you'd need to fix the args, so you'd end up with

Code:

script:
  - curl -s https://raw.githubusercontent.com/BigWigsMods/packager/master/release.sh | bash
  - curl -s https://raw.githubusercontent.com/BigWigsMods/packager/master/release.sh | bash -s -- -g 1.13.3

Although you might want to flip the build order so the retail version is shown in the big "Main File" box on the CurseForge files page. (#justnitpickythings)

Quote:

Originally Posted by yess (Post 335065)
Together with the tags for the toc:

Yea, that is correct (looks a bit awkward, I know)

Ketho 02-20-20 01:35 AM

Quote:

Originally Posted by nebula (Post 335145)
You only need that second step (the block after "# run release.sh with arguments") for it to work :p


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
Uploading VendorPrice-1.3.1-classic.zip... Error (422)
{"message":"Validation Failed","request_id":"07C1:101E:B0DCA:E52E2:5E4E3158","documentation_url":"https://developer.github.com/v3","errors":[{"resource":"ReleaseAsset","code":"already_exists","field":"name"}]}


LudiusMaximus 04-15-20 01:23 PM

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


All times are GMT -6. The time now is 10:30 PM.

vBulletin © 2020, Jelsoft Enterprises Ltd
© 2004 - 2020 MMOUI