Hi,
On my side I check "regularly" the Cruise Control (like every month)
because there is some specific sebomd builds. From my experience, builds
have failed quite repetively these last months because of changes in
configure, librairies, and such. People committed change, builds failed,
then corrections were committed, etc. This means that sometimes, when I
see a build that fails, just waiting a few days is enough to make the
build works again :-). I know, this is not a good behavior, and I should
not wait for the others to repair problems (that I did not introduce).
But I would guess that this is pretty a general behavior.
Anyway, I still think CC is a great tool.
Gerald.
On 10/01/2014 03:34 PM, Jason Swails wrote:
> Hi everyone,
>
> Are we still trying to enable/use continuous integration through Cruise
> Control? Every build is now failing because the host machine does not
> have the python-dev package installed. Dan added this protection to
> configure back on Sep. 19, so CC hasn't made it past the configure stage
> on any development branch since then.
>
> CI is an awesome concept (and works great in projects where it is
> adopted), but it doesn't seem to have caught on much with Amber...
>
> All the best,
> Jason
>
--
____________________________________________________________________________
Prof. Gerald MONARD
SRSMC, Université de Lorraine, CNRS
Boulevard des Aiguillettes B.P. 70239
F-54506 Vandoeuvre-les-Nancy, FRANCE
e-mail : Gerald.Monard.univ-lorraine.fr
tel. : +33 (0)383.684.381
fax : +33 (0)383.684.371
web : http://www.monard.info
____________________________________________________________________________
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Wed Oct 01 2014 - 10:00:02 PDT
