Although I spend little time on Cloubees, its jenkins instance seemed slow and unresponsive to me. Pixie, the host on which lognack.qos.ch/jenkins runs is rather outdated and slow as well but still faster than the Cloudbees' Jenkins instance. More importantly, the logback build is unstable on both Jenkins instances (contrary to builds run on faster machines which are much more stable.). Truth be told, I am not too keen on managing a Jenkins instance on pixie. As a side note, pixie runs Gentoo Linux -- quite a remarkable piece of software. With the hope of installing Jenkins via a Gentoo package, I embarked upon an OS (Gentoo) update which ended up being a major time sink. Ironically enough, no Jenkins package was available after the update and 30h of work. :-) Packages changing their configuration directives in an incompatible way were a major pita during the update. Postfix and Dovecot deserve particular mention in this regard. To cut a long story short, if you would like access on Jenkins running on pixie, please sign up [1] and drop me a note. I'll gladly grant the appropriate privileges. Cheers, [1] http://logback.qos.ch/jenkins/signup On 09.04.2013 02:10, Tony Trinh wrote:
Hi Ceki,
Is the CloudBees Jenkins instance [1] no longer "official"? Why the switch?
[1] https://logback.ci.cloudbees.com/job/logback/
Tony
On Mon, Apr 8, 2013 at 1:34 PM, ceki <ceki@qos.ch <mailto:ceki@qos.ch>> wrote:
Hi all,
FYI, the Jenkins instances at http://logback.qos.ch/jenkins/ is now integrated with github so that a push on https://github.com/qos-ch/__logback/ <https://github.com/qos-ch/logback/> triggers a build.
-- Ceki 65% of statistics are made up on the spot
-- Ceki 65% of statistics are made up on the spot