On Wed, Mar 24, 2021 at 4:43 AM Alexander von Gluck IV
<kallisti5@xxxxxxxxxxx> wrote:
March 23, 2021 5:22 PM, "saloni goyal" <salonig1212@xxxxxxxxx> wrote:
On Wed, Mar 24, 2021 at 12:37 AM Adrien Destugues
<pulkomandy@xxxxxxxxxxxxx> wrote:
When a code or patch set is updated or created then the build runs in
Jenkins for the code and if the build is successful then Verified
label is updated and +1 is voted and code review is permitted only
after verified label is updated and similarly after every new change
the verified label gets reset and updated according to the latest
build. Is this the part of the expected outcome? Please confirm.
We are currently using Concourse for building. What is your plan? Will you
investigate
using Concourse for coding style checks instead of Jenkins? Should we
migrate all our
existing builds to Jenkins? Should we use both tools side by side for
different needs?
I have not used concourse yet but I think according to our
requirements Jenkins can be used also it provides a number of plugins
that might be helpful in future.
Jenkins does not fill our needs. We do all of our builds within docker
containers with some pretty advanced pipelining. We build our toolchains
(every potential architecture) into "build containers". We then use those
build
containers to compile Haiku.
This lets us generate and keep an archive of "master", "r1beta1", "r1beta2",
"r1", "r2" etc build containers ensuring we can always build previous releases
of Haiku long after the buildtools repo moves on.
(It's the sole reason we can still do r1beta2 updates today)
We used to use buildbot and this was a huge gap we had for a long time.
If anyone has any resources or way to integrate gerrit with concourse
then please share.
It needs to be written. That's part of this proposal. The plugin system in
concourse is pretty advanced and allows resource containers to be "pretty
much any language"
