[CCC DEV] Travis CI?
matt at jadud.com
Wed Apr 24 16:36:33 BST 2013
It worked. It needs a tweak or two yet, but it will do the job, I think.
You can click on the #1 and see the result of the build. It failed, and
incorrectly reported it succeeded, but given the overhead to get this
working, I'd say this will be worthwhile.
Well, until I find a show-stopper. I don't know why the error code came
back 0 (it used the "fail" function in the script, which should exit with
code 1), but that's small.
I'll continue to explore it in my fork, and will make a request when it
works. A buildbot/CI server is really valuable on multiple fronts. Once we
have it working, anyone can then
1. Fork the repos
2. Make changes.
3. Enable Travis for their fork of the repos (it's simple), and
4. Know whether their proposed merges break the build on a clean system or
More later, when I've figured things out.
(I know it seems like I'm going in 1000 directions at once... I'm not
trying to, per se, but I am trying to get myself in a position to kick of
summer research in a few weeks, which is the general thrust of my poking
and questioning lately.)
On Wed, Apr 24, 2013 at 11:26 AM, Martin Ellis <ellism88 at gmail.com> wrote:
> I tried to have a play didn't read well enough, gave up.
> On Wed, Apr 24, 2013 at 4:25 PM, Matt Jadud <matt at jadud.com> wrote:
>> I'm giving it a go on my fork.
>> We could tweak the existing build script to take a --travis flag, which
>> would eliminate the "install" step. (I don't know if running the install
>> step is good on the CI platform or not. I'm still reading.)
>> It's unclear to me why concurrency/kroc is in my list of systems that
>> have been built...
>> But, if this works well for us, that is what I'd want to see building
>> On Wed, Apr 24, 2013 at 9:40 AM, Christian Jacobsen <cljacobsen at gmail.com
>> > wrote:
>>> Travis looks generally good and like what a lot of open source projects
>>> On 24 April 2013 11:42, Matt Jadud <matt at jadud.com> wrote:
>>>> Hi all,
>>>> We used to have a buildbot. I don't have the bandwidth at this time to
>>>> maintain/host one.
>>>> Would Travis, or some other similar (free, ideally) service suffice for
>>>> giving us back the ability to test, at the minimum, a Linux 32- and Linux
>>>> 64-bit build?
>>>> developers mailing list
>>>> developers at concurrency.cc
>> developers mailing list
>> developers at concurrency.cc
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the developers