Add Travis CI for compilation check #15
Conversation
Expected to fail due to the lack of autoconf-archive.
The approach is to use the tarball for the 2017.03.21, as it's the minimal version for dash-version policy of AX_IS_RELEASE macro. Although we can use APT to install autoconf-archive, but it won't work for OSX build, and cloning Git takes more time than a simple tarball.
|
Looks good. I don't see a benefit to caching, as it should be faster to download the |
livibetter
force-pushed
the
add-travis-ci
branch
from
97b5021 to
7af1bbb
Compare
|
The commit for caching is removed. (build result) |
|
Excellent -- nice work. Is there anything extra that needs to be configured to set this up? |
|
Not sure if it's same for repo in organization, but in personal account, I do like:
Once turned on, the CI will build on the next push. |
|
Okay, I've requested organisation access via the Travis CI website. For some reason, my account has been flagged as abusive (??? -- I only just signed up, and I just tried build a fork of pipes.c) so I will have to wait for support to get back to me. |
|
@StefansM That's weird. I hope you get that sorted out soon and no harms done to your account. But who flagged you? GitHub or Travis CI? And I've just received an email about Travis CI requests access to our private data, which link did you click on? I am holding off the request for approval because I don't want to grant the access to the private data, even we have none, if you did click on the wrong one, which I'd believe so, although I have no experience of turning on in a organization's repo. |
|
@livibetter Yes, very strange. It's Travis CI that flagged me. I hope to hear back from them soon, otherwise I guess I'm stuck. I thought I used |
|
@StefansM done. |
|
OK, I've resent the request. |
|
I heard back from Travis CI support in impressively quick time. Apparently they were making some changes to their infrastructure and mistakenly flagged my account. All fixed now and set up. |
AX_IS_RELEASE(dash-version)).Here is the build result.
As we don't have tests (well, not sure how we can do that), this CI is only for the compilation and
make install. Invoking Snakes with-h(or-vsoon) wouldn't mean much, nor would{ sleep 0.1 ; yes ; } | ./snake(with #14), it runs and that's all.The caching actually slows down each build for about 10 to 20 seconds, but it won't be downloading autoconf-archive 4 times in every push.
I honestly don't know if we should cache or not, if @StefansM prefers not, I can remove the commit for caching.