Re: [Orekit Developers] Continuous integration

Great news. As for notifications, I would prefer to keep the developers list for people and not use it for automatic notifications. Is there a way we could notify the person who created the commit that broke the build? There have been a few times where I've forgotten to run the checkstyle report before committing and I think a reminder/notification would be helpful.

Best Regards,
Evan

On 09/30/2015 08:57 AM, Hank Grabowski wrote:

Awesome news! CI is like unit tests is like source code management systems...once you work with them you wonder how you got along with out it...

On Tue, Sep 29, 2015 at 3:07 PM, MAISONOBE Luc <luc.maisonobe@c-s.fr> wrote:

Hi all,

Our great sysadmin, Sébastien, has just finished setting up a continuous integration
server for our projects. Both Orekit and Rugged are now automatically recompiled and
all the tests run after each commit on the master branch. When branch MATH_3_X of
Apache Commons Math is changed, Orekit and Rugged are also rebuilt, but in this case
it is not immediate, we simply poll the git server once per day.

The output of the build can be found here:

<https://www.orekit.org/jenkins/>

You will notice a few glitches (typically the checkstyle results for Rugged are
wrong, it seems the default rules are checked instead of the configured rules),
this will be fixed soon.

For now we did not trigger automatic notification of build errors, what do you
think we should do? We could have build errors sent directly to the developers
list, or we may simply send them to a people who want to be notified (typically
the core developers).

best regards,
Luc