Can we add drone.io and status badge?
While I can set up drone.io for my own fork of gd-libgd, drone.io does not let me set up CI for the official repo (I assume because I lack push permissions or something).
It takes about 5 minutes to set up Drone.io on a repository. Once that is done, I would like to add a readme file and a status badge so it's obvious when the build gets broken.
Comments (33)
-
-
reporter Drone.io appears to be abandoned; their VMs are broken and spewing errors. I can set up AppVeyor, but if you want reliable linux/mac builds and artifacts, we'd have to move to github. (Travis is github-only)
-
I do not understand why they want github, can you explain pls?
-
reporter Travis uses GitHub's authorization system to determine who can do what. This makes it very easy to manage projects, as you only have to manage permissions in GitHub. When you're using advanced services that require encrypted tokens (like releasing artifacts to github releases, or coverity scan, etc), this is very nice.
The upside, Travis+GitHub is a super-smooth, fast, experience. It's open-source and the best-maintained CI service I've seen.
The downside, it is tied to GitHub. GitLab compatibility might be possible, but the design is intentionally married to GitHub.
Most paid CI services advertise 'travis.yml' compatible. I'm paying $80/mo for AppVeyor, but Travis is so fast - and free - that I'm not inclined to pay for vexor.io or something similar knockoff when I can get the real thing.
-
We could setup a mirror on github only for that, thoughts?
-
reporter It wouldn't automatically test every pull request, which (to me) is a big feature. (also; one of those things that you can only do when you tightly integrate with the git provider, like travis does).
I really like bitbucket, but GitHub's giant ecosystem has strong gravitational pull. It does also have really good multi-factor authentication, which I promote the use of.
There's also the convenience factor; if libgd was on GitHub, we would sync our copy much more frequently, since it takes seconds via browser (instead of minutes via commandline), and we could easily view changes between branches on different repos. Right now, we usually end up with a painful rebase before each upstream push :[. That does discourage PR frequency.
I'd also like to invest in a 'CONTRIBUTING.md' file eventually; this (on GitHub) is displayed to users filing issues or PRs, so that they can keep code style, etc. consistent. Making the onboarding process easier and getting more devs to jump in would be nice; as would setting up waffle.io and marking tasks as 'up for grabs'. (Example on ImageResizer) But this too, is GitHub specific.
Mirroring is certainly better than nothing, though!
-
hm... That's bad.
I am not too keen to do yet another move. While github is very appealing, I do not have the time to transfert everything, keep history (git) and all that :/
Any suggestions welcome :)
-
reporter We could help with that; actually. We have around 50 projects to manage, so we've developed some pretty fast processes.
-
yes, let me check with the other if they are ok to move.That will also bring more visibility :)
-
ok, Ondrejm, Remi and Chris are all OK
Next step? :)
-
Account Deleted Converting the repositories is easy - e.g. done.
Now I am working on travis-ci.org build of the pelican website (I wouldn't mind converting the pages to native github Jekyll... but I am not doing that :)).
The next step would be to:
1) setup CI build at travis-ci.org (easy, I will do that as soon as I finish the website) 2) setup Coverity build from travis-ci.org (and drop the custom jenkins at CZ.NIC) 3) setup push mirroring over to bitbucket (should be fairly easy) 4) change various information on the website, etc.
-
@nathanaeljones what is your github handle? :)
And email, would be handy :)
@oerdnj O_o wow :) Thanks :)
-
Also converting issues :/
-
Account Deleted One more thing - we probably need to migrate the issues. I found this: https://github.com/vbabiy/bitbucket_issue_migration, but it seems to lack support for "organization" repositories as it asks for "password" for the "libgd" user. I'll look into it unless somebody beats me to it.
-
Account Deleted So, website is up and running on libgd.github.io. You can either setup alias from libgd.org (there should be a CNAME file in website root) or just do the redirect.
Travis CI on libgd fails with something webp related. Perhaps the setup is missing some library. I also changed .travis.yml to use autotools on linux.
-
reporter Add tostercx to the repo, he can fix the build. A few important commits didn't make it upstream after we updated some dependency locations, thus the issues. My github is nathanaeljones.
-
reporter Re: issue migration, this is a problem on the bitbucket/read side, right? A hacky fix would be to transfer the repo to an individual, then back to the org (assuming bitbucket permits that).
-
@nathanaeljones, they are using autotools atm. The error seems to have something to do with the vpx->webp switch.
edit
Hmm.. runs fine locally.
-
reporter Does thumbs.sh build? Seems better to fetch deps than rely on travis's worker's copy.
-
reporter Also, I can let libgd\libgd use my upgraded AppVeyor account, but I will have to be an org member for AppVeyor to recognize it.
-
@oerdnj, you're right - it's probably a missing dep. libwbp-dev is packaged only for ubuntu 14, travis is running 12. There's a few more failing the apt-get. That's probably it.
@nathanaeljones, it should work after applying https://github.com/imazen/gd-libgd/commit/82d7530e6fe0ef861218576c99be4dbce7104299 There were a few more updates for osx after that tho.
-
Ideally if we could test both CMake and auto conf builds, that would be awesome :)
-
Probably unrelated but there's an outdated macro: https://bitbucket.org/libgd/gd-libgd/src/ba081d9141e5ab5f8db5c4704ba141592dfa879b/src/gd_filename.c?at=master#cl-73
-
Oh I forgot it. That will be for 2.2
Btw, we need to test GD-2.1 too, not as frequently as there won't have many changes but bugs fixes.
-
On the todo list, the releases have to be transferred as well.
@oerdnj I will change the alias entry to point to github.io
Thanks for the quick&awesome work :)
-
reporter @oerdnj The GitHub invitation you sent me was broken - resend?
-
forward domains updated for www.libgd.org and libgd.org to libgd.github.io
Thanks!
-
@oerdnj are you on the issues transfert? Only missing to finalize the move :)
-
Account Deleted Got sidetracked :). If anyone has a time to look at it, I won't mind. @nathanaeljones ?
-
reporter I'm working on it, but API rate limits are making it difficult -> https://github.com/imazen/bitbucket_issue_migration
-
reporter It looks like the rate limits don't apply to private repos. Making the repository private (temporarily) during the import should make this possible. It would also prevent @notifications from happening to everyone, which is annoying.
I just completed a test against a blank private repo and all 140 were migrated. If someone can give me Owner access, I'll use my card to enable private repos, and get this done.
@oerdnj @pierrejoye
-
reporter GitHub support got back to me finally and lifted my rate limit. Let me know if you spot any issues with the issues :)
-
@nathanaeljones Thanks! Look all good!
I think we are good to move!
- Log in to comment
Please do it :)