Date: Wed, 22 Feb 2017 19:10:19 +0800 From: Li-Wen Hsu <lwhsu@freebsd.org> To: Oleksandr Tymoshenko <gonzo@bluezbox.com> Cc: Alan Somers <asomers@freebsd.org>, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: TravisCI vs BuildBot vs Bamboo vs Jenkins Message-ID: <CAKBkRUytTXeu2dppQbAz7ujPgqFR7371BFG1EnA4XiQ%2BQxJ1Dg@mail.gmail.com> In-Reply-To: <20170222065408.GA19302@bluezbox.com> References: <CAOtMX2jbEk-T5-vq%2BcAWDKJ578%2Bx9CeTHKVgt9k-=92bgGi7Pg@mail.gmail.com> <20170222065408.GA19302@bluezbox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 22, 2017 at 2:54 PM, Oleksandr Tymoshenko <gonzo@bluezbox.com> wrote: > FreeBSD's CI is built using Jenkins: https://ci.freebsd.org also > https://wiki.freebsd.org/Jenkins so it must be working fine with > FreeBSD. > > I've been using Jenkins for number of years (not in *BSD world though) > and I kind of like it despite somewhat trashy UI. My main complaint is > that you can't have CI pipeline description/settings in file in version > control (like in GitLab for instance) and have to set it up manually > via web UI or API. Other than that it's fairly good system. > =E2=80=8B=E2=80=8B > =E2=80=8Bci.freebsd.org uses Jenkins Job Builder from OpenStack: https://docs.openstack.org/infra/jenkins-job-builder/ by which you can define your jobs in YAML and save them in VCS. Jenkins 2 also offers "pipeline as code" feature by which you can control your jobs more: https://jenkins.io/doc/book/pipeline/ Best, Li-Wen=E2=80=8B --=20 Li-Wen Hsu <lwhsu@FreeBSD.org> https://lwhsu.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKBkRUytTXeu2dppQbAz7ujPgqFR7371BFG1EnA4XiQ%2BQxJ1Dg>