I'm a total newbie to travis-ci, but both it and redline looked
interesting to me, so I thought I would give it a shot.
There are probably a couple of things that are worth setting up:
Blacklisting or whitelisting branches, email notifications on
failure/success. Doc is here
http://about.travis-ci.org/docs/user/build-configuration/As far as actual building goes, I don't think there is much left to do
once the project is set up to use maven.
I see a few people have also included travis build status in their
README.md. Copy/paste markdown is available when clicking on the cog
drop-down thingy on the repository page at travis. FWIW, the markdown
for my fork is:
[](
http://travis-ci.org/msandiford/redline-smalltalk)
Cheers,
Martin
On Thu, Feb 23, 2012 at 11:43 AM, Sean T Allen
<
[hidden email]> wrote:
> Thanks again Martin.
>
> Pull request merged.
>
> I saw in your comment that it was a fairly simple setup and more could be
> done.
> Do you have any suggestions are you know more about Travis CI than we do?
>
> -Sean-
>
> On Wednesday, February 22, 2012 at 12:55 AM, Martin Sandiford wrote:
>
> Err. OK. That was ridiculously easy.
>
> I think you should be able to see the results here for redline-
> smalltalk:
>
http://travis-ci.org/#!/msandiford/redline-smalltalk>
> New to travis ci - I just had to add the .travis.yml file and push.
>
> Cheers,
> Martin
>
> On Feb 12, 8:35 am, Sean Allen <
[hidden email]> wrote:
>
> Hey All,
>
> Slowly easing back into redline things after a work created hiatus. Before
> I disappeared 6 weeks ago I was about to send an email
> to see if there was anyone who wanted to get involved by seeing what would
> be required ( and then implement anything needed )
> to get support to build both redline and redline projects in TravisCI.
>
>
http://travis-ci.org/>
> Hopefully this is interesting to someone out there on the list.
>
> More coming soon.
>
> -Sean-
>
>
Locked
