Excerpts from Brett Smith's message of 2014-08-24 16:56:49 +0200: > In order to maintain visibility into processing Fedora 20 we will need a > Jenkins server. > This way the updates, groupbuilds can all be scheduled and monitored by more > than a few. > Not sure where to start with this.
what are the system requirements to controll the updates and builds? could they be run from remote from any kind of machine? or does it require a machine under conary control? if it can be done from remote then maybe a public jenkins server like https://buildhive.cloudbees.com/ could do the trick. that would provide even more exposure than just having our own server that noone knows about unless we advertise it. if purely remote is not possible, i am potentially interested to help hosting a jenkins server. i am using buildhive for pike and it suffers from the fact that buildhive, as set up, doesn't distinguish between a failed build and a failed test. (i don't believe this is an issue for foresight though) i could run it on my server once i have that ready and share access, or if you don't mind sharing the server with a few other Free Software projects (only pike and sTeam (a collaboration-platform written in pike) at this point) i could help with hosting it on a foresight server. greetings, martin. -- eKita - the online platform for your entire academic life -- chief engineer eKita.co pike programmer pike.lysator.liu.se caudium.net societyserver.org BLUG secretary beijinglug.org foresight developer foresightlinux.org realss.com unix sysadmin Martin Bähr working in china http://societyserver.org/mbaehr/ _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
