Quote:
https://github.com/Rainrider/oUF_Dis...er/.travis.yml (Sorry for the late response, I seem to have missed your reply.) |
Quote:
|
Quote:
I switched over because after TravisCI merged org to com my GitHub organization (where all my addons are hosted) got screwed up, and TravisCI support couldn't help me with it and told me to just wait for the merge to go through by itself (which could take months), so it was more of a necessity for me. We still use TravisCI for oUF, and there's no real need to change. |
Regex string
Hey, thanks for the great tutorial!
The only thing I would love to get some help with is the regex string, as I cant get it to work. x) The format I usually use for my versions is either a tag with 8.0.1.18 for a full release or 8.0.1.18-alpha/beta for beta/alpha releases. Any help with this would be wonderful! With regards, Dajn |
Quote:
Code:
/^\d+\.\d+\.\d+\.\d+(-\w+)?$/ |
Quote:
Been trying to get the hang of regex lately as I will start use it at work a lot, so this tutorial was a step in the right direction to start to learn it. :) With regards, Dajn |
Hey p3lim I'm having an issue where the packager isn't uploading properly to wowinterface.com
My tags are in the following format. v5.4, v.5.5, v5.6 etc.. so I changed the regex to the following Code:
/^v?\d+\.\d+(\.\d+)?(-\S*)?$/ So I then added a .pkgmeta file but left it empty. That didn't seem to work. So I'm thinking that something needs to go into this file. I don't need externals or anything. Just simply upload the addon as is to wowinterface. BTW: Yes I did make the modifications to the .toc file and added the addon IDs for both curse and wowinterface.com Code:
## X-Curse-Project-ID: 28603 |
Lol!!!!
Quote:
Code:
|
Quote:
Happy it all works for you :). |
Trying to get this setup myself and not having much luck with the regex even tho it should work :/
Currently they get tagged as vA.B.C(.D) so can be v8.0.0 or v8.0.0.1 Trying - ^v\d+.\d+.\d+(.\d+)?$ which works in any self-tests I do, but on Travis i'm getting 'Branch "v8.0.1.4" not included per configuration.' What have I done wrong? :) |
1 Attachment(s)
Quote:
Could you show me your .travis.yml file? |
Quote:
Code:
sudo: false Bah I think I see the problem already... forgot the /'s |
Quote:
I mentioned an alternative to the Travis method here, which eliminates the need to verify tag structure (it just assumes any tag is a release-ready version). (Plus, it's easier to set up and expand upon ;)) |
3 Attachment(s)
Thanks p3lim for providing this. I need some help.
I added the .travis.yml and the .pkgmeta to one of my addons in my github repo. Currently the .pkgmeta and the .travis.yml use CRLF as ending. Is that a problem? I told GIT bash for windows not to mess with line endings. https://github.com/zorker/rothui/tre...w8.0/rVignette I then used the git command you provided using git bash for windows in the git directory of rVignette. I'm not sure but I think my whole repo got that tag?! Is that correct? https://github.com/zorker/rothui/tree/v800.20181025 Once I started the git bash command I had to log into github and the tag completed. But nothing else seem to have happened? What am I missing? I had added the wowi token to the Travis page before. My travis page is all grey and says: There is no build on the default branch yet? Ok I checked the travis request page. I can see some error messages now. Travis does seem to try to generate a new build when I commit with Github desktop to master. (The first two requests) Why is that? *edit* Ohhh I see. It would run on any commit but when reading the config file would only react to branches that match the pattern. That being said. To correct the error from my understanding I have to put the .travis.yml in the repo root right? What does that mean for the packager? Will he parse all directories and upload all of them at once? If I only make a change to one of the addons all will be updated? How do I do this for specific directories? |
Quote:
E.g, if you tag the repo (and tags only work on repo-level, as with branches), every project you have in that repo (as you've set it up) will get the same tag. The packager and Travis expects Git to be used as it was intended; one repo per project, and each project has its own .travis.yml file at the root, and tagging the repo will trigger Travis/packager. |
It relates back to Google Code and SVN days. When Google Code closed there was an option to move all of it to Github which I did.
That is why there is one huge mono repo for all of it. Never saw a reason to change that. |
Quote:
If you ever want to manage dependencies, external tooling, collaboration, or versioning (just to name a few), monorepos is going to become a problem, fast. My suggestion to you is to spend some time splitting up your single repo into multiple, preferably one per addon, then you'll be able to fully utilize Git as it was intended, which includes being able to use the packager with TravisCI in an automated fashion. Example of splitting while preserving history: https://www.atlassian.com/blog/git/t...sitory-git-way |
Right, it would appear I'm doing something wrong with git, and I can't quite figure out what, so I'm turning here for help. Even tagging exactly in the manner suggested in the op, I keep tripping this:
Code:
if [ -z "$TRAVIS_TAG" ]; then I'm sure there's something obvious I'm missing, but I'm stumped, so any help would be appreciated. The repo in question is at https://github.com/Aiue/AQT, in case an extra set of eyes looking at stuff helps. |
Quote:
|
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 |
All times are GMT -6. The time now is 05:27 PM. |
vBulletin © 2024, Jelsoft Enterprises Ltd
© 2004 - 2022 MMOUI