Re: [LMMS-devel] Continuous integration building

[Lukas W. <luk...@gm...>]

@ All
When committing to LMMS, you can prevent triggering a CI build by
adding [skip ci] to the commit message (doesn't have to be in the
first line). An use case for this is for example updating the readme
file.

And updating the readme file is exactly what I'll do next. Using a
markdown readme, we can include a neat little icon that states whether
the build passed or not. You can just see it on the main page this way
(https://github.com/LMMS/lmms/).

@ Jonathan
By default, you'll only receive notifications when the build fails or
was broken and then was fixed. See
http://docs.travis-ci.com/user/notifications/
Guess we'll not see if it does work until we really break the build
some day. We could also change it to always sending emails after each
build, but that would be quite annoying.

2014/1/21 Jonathan Aquilina <eag...@gm...>:
> Me and Lukas have setup Travis CI with the git hub repo and its working
> smashingly.
>
> Just to give everyone a heads up on what to expect.
>
> The one thing is that the committer will recieve the email that they have
> broken something and to look into why their commit broke the build
>
> @lukas I didnt recieve an email even about a successful build. Can you confirm
> that others that should recieve the emails dont need to be listed in the yaml
> file please.
>
> Thanks
> Jonathan
>
> ------------------------------------------------------------------------------
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> _______________________________________________
> LMMS-devel mailing list
> LMM...@li...
> https://lists.sourceforge.net/lists/listinfo/lmms-devel