One ideal end result IMO would be that some service similar to GNOME continuous that validates any commit or patch ahead of time. If a commit wasn't validated and somebody tried to push it to master, the server should reject it. (GitLab does this implicitly with protected branches and merge requests, GitHub lately got something similar too.) I personally would love to have a bot that listens to bugzilla and tests all patches automatically; also any pushed branch should be tested automatically.
Testing code and buildability should be as simple as submitting or pushing a patch. 2016-01-22 14:13 GMT+01:00 Alberto Ruiz <ar...@gnome.org>: > Another thing that would be really useful in this line is to be able to > submit specific branches for testing. Say I'm working on wip/foobar to avoid > breaking master, and before pulling that stuff from master I want to make > sure I won't break the builds. > > Is anything like this possible at all? > > 2016-01-22 13:03 GMT+00:00 Simon McVittie <simon.mcvit...@collabora.co.uk>: >> >> On 21/01/16 14:54, Emmanuele Bassi wrote: >> > In short, I want to ensure that GNOME maintainers become >> > a bit more proactive in giving a crap about their modules breaking on >> > something that is not their own computers. >> >> Is there a way in which contributors/maintainers can reproduce something >> equivalent to what Continuous would build (or a large enough subset of >> the dependency stack to reach their packages), in a local virtual >> machine where they can debug issues interactively? >> >> In the autobuild systems that I've worked with, I've found that the key >> feature that makes them most useful is to avoid "magic" centralized >> infrastructure that only a few sysadmins/maintainers can access. >> >> For instance, one of the things I really like about Debian's autopkgtest >> initiative (a package-oriented and potentially system-level equivalent >> of GNOME installed-tests) is that it's quite well-documented how to get >> a local mirror of the environment in which tests are run on the official >> infrastructure[1] and how to get something basically equivalent as a >> virtual machine image[2]. >> >> [1] https://ci.debian.net/doc/file.MAINTAINERS.html >> [2] http://manpages.debian.org/cgi-bin/man.cgi?query=adt-virt-qemu >> >> -- >> Simon McVittie >> Collabora Ltd. <http://www.collabora.com/> >> >> _______________________________________________ >> desktop-devel-list mailing list >> desktop-devel-list@gnome.org >> https://mail.gnome.org/mailman/listinfo/desktop-devel-list > > > > > -- > Cheers, > Alberto Ruiz > > _______________________________________________ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/desktop-devel-list _______________________________________________ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
