Re: [MiNT] rpm

[Matthias Arndt <marndt@asmsoftware.de>]

Am 19. Dezember 2014 23:18:50 MEZ, schrieb "Thomas Jürges" <thomas@senmut.net>:

On 2014-12-19 21:29, Peter Slegg wrote:
[...]
 Whaever the technology, a central system that can quickly build the rpm
 and report errors would be a great advantage.

Jenkins [http://jenkins-ci.org/] comes to my mind.  Jenkins runs on any
host system that provides a Java virtual machine - given that it has
more than 1MB of memory :-) -.  Jenkins jobs could be set up for
cross-compilation and/or for building RPMs.  RPMs could be built only if
a build of the source was succssful.  Builds of software could be
triggered manually, automatically when monitoring VCS, regularly at time
intervals and what not.  The possibilities and options are endless!


Cheers
 T.

We use Jenkins at work to build embedded software and accompanying unittests. It works great and has a lot of features through plugins.
It takes some time to get into it and a system admin but it really works great when configured.

It could be a great solution to automate builds  of packages. When used with Subversion, it can trigger builds that depend on libraries. E.q. you change a linked library and all targets using this lib as an external are rebuild aswell. Great for regression tests!

Regards,
Matthias
-- 
http://final-memory.org